Template:Green

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.10/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.10/ http://www.mediawiki.org/xml/export-0.10.xsd" version="0.10" xml:lang="en">
  <siteinfo>
    <sitename>REACHBACK</sitename>
    <dbname>reaper_db715167</dbname>
    <base>http://www.reachback.io/wiki/index.php?title=Knowledge_Center</base>
    <generator>MediaWiki 1.27.1</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">REACHBACK</namespace>
      <namespace key="5" case="first-letter">REACHBACK talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
      <namespace key="102" case="first-letter">Property</namespace>
      <namespace key="103" case="first-letter">Property talk</namespace>
      <namespace key="104" case="first-letter">Type</namespace>
      <namespace key="105" case="first-letter">Type talk</namespace>
      <namespace key="106" case="first-letter">Form</namespace>
      <namespace key="107" case="first-letter">Form talk</namespace>
      <namespace key="108" case="first-letter">Concept</namespace>
      <namespace key="109" case="first-letter">Concept talk</namespace>
      <namespace key="170" case="first-letter">Filter</namespace>
      <namespace key="171" case="first-letter">Filter talk</namespace>
      <namespace key="2300" case="first-letter">Gadget</namespace>
      <namespace key="2301" case="first-letter">Gadget talk</namespace>
      <namespace key="2302" case="case-sensitive">Gadget definition</namespace>
      <namespace key="2303" case="case-sensitive">Gadget definition talk</namespace>
    </namespaces>
  </siteinfo>
<page arvcontinue="">
  <title>Template:Green</title>
  <ns>10</ns>
  <id>107</id>
  <revision>
    <id>255</id>
    <timestamp>2009-06-22T12:37:39Z</timestamp>
    <contributor>
      <username>Al Maghi</username>
      <id>0</id>
    </contributor>
    <comment>Created page with '&lt;span style="color:green"&gt;{{{1}}}&lt;/span&gt;&lt;noinclude&gt; [[Category:Formatting templates|{{PAGENAME}}]] &lt;/noinclude&gt;'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="111" xml:space="preserve">&lt;span style="color:green"&gt;{{{1}}}&lt;/span&gt;&lt;noinclude&gt;
[[Category:Formatting templates|{{PAGENAME}}]]
&lt;/noinclude&gt;</text>
    <sha1>5fce00bbe0789ccf092ee46ffbef5e1c16127e2f</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Category:Mediawiki.org Formatting templates</title>
  <ns>14</ns>
  <id>100</id>
  <revision>
    <id>241</id>
    <timestamp>2009-06-24T00:39:38Z</timestamp>
    <contributor>
      <username>Al Maghi</username>
      <id>0</id>
    </contributor>
    <comment>Created page with '[[Category:Formatting templates]]'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="33" xml:space="preserve">[[Category:Formatting templates]]</text>
    <sha1>b0977d99bfd84d652e4508b3691eb776cf54a6dd</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Category:Cross-browser compatibility templates</title>
  <ns>14</ns>
  <id>102</id>
  <revision>
    <id>245</id>
    <timestamp>2011-06-15T22:40:06Z</timestamp>
    <contributor>
      <username>Edokter</username>
      <id>0</id>
    </contributor>
    <comment>Created page with "This category lists all templates that facilitate in cross-browser CSS support.  [[Category:Formatting templates]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="114" xml:space="preserve">This category lists all templates that facilitate in cross-browser CSS support.

[[Category:Formatting templates]]</text>
    <sha1>e44d93c6a7bddb9c36f79fab0f7dadb21bbe1bf0</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Dummytab</title>
  <ns>10</ns>
  <id>114</id>
  <revision>
    <id>271</id>
    <timestamp>2011-12-03T07:08:39Z</timestamp>
    <contributor>
      <username>Varnent</username>
      <id>0</id>
    </contributor>
    <comment>copy original from wikipedia</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="451" xml:space="preserve">&lt;noinclude&gt;&lt;table&gt;&lt;tr&gt;&lt;/noinclude&gt;&lt;td style="width: {{#if:{{{tab spacing percent|}}}|{{#expr:{{{tab spacing percent}}}/2}}|1}}%; border-bottom: {{#if:{{{border|}}}|{{{border}}}|solid 1px #A3B1BF}}"&gt;{{#if:{{{tab spacing percent|}}}||&amp;nbsp;}}&lt;/td&gt;&lt;noinclude&gt;&lt;/tr&gt;&lt;/table&gt;{{doc|content=

This template is used with {{tl|start tab}} to offset the first and last tabs from the end of the tab bar slightly.

[[Category:Formatting templates]]

}}&lt;/noinclude&gt;</text>
    <sha1>3bda72d47644a9d5c168c612904ba7fd70a1650b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Magnify icon</title>
  <ns>10</ns>
  <id>123</id>
  <revision>
    <id>291</id>
    <timestamp>2011-12-21T08:18:45Z</timestamp>
    <contributor>
      <username>Varnent</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>5 revisions from [[:w:en:Template:Magnify icon]]: used by wide images tempalte</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="131" xml:space="preserve">&lt;div class="magnify"&gt;[[File:Magnify-clip.png|15x13px|link={{{link}}}|alt=|Enlarge]]&lt;/div&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>ec1af95c57fa159203d3904a66a4890f70f4791b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Pagelist</title>
  <ns>10</ns>
  <id>113</id>
  <revision>
    <id>269</id>
    <timestamp>2012-01-07T01:05:16Z</timestamp>
    <contributor>
      <username>Varnent</username>
      <id>0</id>
    </contributor>
    <comment>full use of nspace=default</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4792" xml:space="preserve">&lt;includeonly&gt;{{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{1}}}}}|{{{1}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{1}}}}}|{{{1}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{2|}}}|{{#if:{{{3|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{2}}}}}|{{{2}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{2}}}}}|{{{2}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{3|}}}|{{#if:{{{4|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{3}}}}}|{{{3}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{3}}}}}|{{{3}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{4|}}}|{{#if:{{{5|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{4}}}}}|{{{4}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{4}}}}}|{{{4}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{5|}}}|{{#if:{{{6|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{5}}}}}|{{{5}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{5}}}}}|{{{5}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{6|}}}|{{#if:{{{7|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{6}}}}}|{{{6}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{6}}}}}|{{{6}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{7|}}}|{{#if:{{{8|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{7}}}}}|{{{7}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{7}}}}}|{{{7}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{8|}}}|{{#if:{{{9|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{8}}}}}|{{{8}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{8}}}}}|{{{8}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{9|}}}|{{#if:{{{10|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{9}}}}}|{{{9}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{9}}}}}|{{{9}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{10|}}}|{{#if:{{{11|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{10}}}}}|{{{10}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{10}}}}}|{{{10}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{11|}}}|{{#if:{{{12|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{11}}}}}|{{{11}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{11}}}}}|{{{11}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{12|}}}|{{#if:{{{13|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{12}}}}}|{{{12}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{12}}}}}|{{{12}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{13|}}}|{{#if:{{{14|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{13}}}}}|{{{13}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{13}}}}}|{{{13}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{14|}}}|{{#if:{{{15|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{14}}}}}|{{{14}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{14}}}}}|{{{14}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{15|}}}|{{#if:{{{16|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{15}}}}}|{{{15}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{15}}}}}|{{{15}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{16|}}}|{{#if:{{{17|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{16}}}}}|{{{16}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{16}}}}}|{{{16}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{17|}}}|{{#if:{{{18|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{17}}}}}|{{{17}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{17}}}}}|{{{17}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{18|}}}|{{#if:{{{19|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{18}}}}}|{{{18}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{18}}}}}|{{{18}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{19|}}}|{{#if:{{{20|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{19}}}}}|{{{19}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{19}}}}}|{{{19}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{20|}}}|&lt;nowiki&gt; &lt;/nowiki&gt;and {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{20}}}}}|{{{20}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{20}}}}}|{{{20}}}]]}}{{{edelim|{{{delim|}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}&lt;!--
--&gt;&lt;/includeonly&gt;&lt;noinclude&gt;
{{documentation}}
&lt;!-- PLEASE ADD CATEGORIES AND INTERWIKIS TO THE /doc SUBPAGE, THANKS --&gt;
&lt;/noinclude&gt;</text>
    <sha1>b956a9df1246a29c44995c86ca9daee3c4830035</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Cartella</title>
  <ns>10</ns>
  <id>115</id>
  <revision>
    <id>273</id>
    <timestamp>2012-02-11T12:33:20Z</timestamp>
    <contributor>
      <username>Varnent</username>
      <id>0</id>
    </contributor>
    <comment>finalize mods for no links usage</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2490" xml:space="preserve">{| style="width:100%; margin-bottom:.5em; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"
&lt;!-- 1 --&gt;
| rowspan="2" nowrap="nowrap" width="1%" height="37px" valign="top" style="background:#FFF; border:2px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|ABCDEF}}; border-bottom:0; padding:0; padding-right:1em; margin:0; {{border-radius|0 1em 0 0}}" | [[File:cartella_{{#switch:{{{1|}}}|blu=blu|grigio=grigia|verde=verde|viola=viola|arancione=arancione|rosso=rossa|blu}}.jpg|link=|Background]] &lt;div style="margin-top:-31px; padding-left:12px"&gt;[[File:{{{logo|Nuvola apps kalzium.svg}}}|{{{px|22}}}px]]&lt;/div&gt;&lt;div style="padding-left:43px; margin-top:-{{{heightpx|{{#expr:{{{px|22}}} + 4}}}}}px; font-size:130%"&gt;'''{{{titolo}}}'''&lt;/div&gt;
&lt;!-- 2 --&gt;
| height="10px" |
|-
&lt;!-- 3 --&gt;
| class="plainlinks" valign="bottom" style="border-bottom:2px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|ABCDEF}}; text-align:center"| {{#if:{{{link|}}}|&lt;div style="float:left; padding:0 .5em 0 .5em; {{border-radius|0 5em 0 0}} border:1px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|ABCDEF}}; border-left:0; border-bottom:0; background:#{{#switch:{{{1|}}}|blu=ECF5FF|grigio=E3E3E3|verde=CEF2E0|viola=EAEAFF|arancione=FFE9D2|rosso=FFD1D1|ECF5FF}}; font-size:85%"&gt; [{{fullurl:{{{link}}}|action=edit}} edit]|&lt;div style="width:100%;"&gt;&amp;nbsp;&lt;/div&gt;}}
&lt;/div&gt;
|-
&lt;!-- 4 --&gt;
| colspan="2" style="padding-left:.5em; padding-right:.5em; background:#FFF; border:2px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|ABCDEF}}; border-top:0; border-bottom:0" |
{{{contenuto}}}
|-
&lt;!-- 5 --&gt;
| colspan="2" class="radius_bottom" style="background:#{{#switch:{{{1|}}}|blu=ECF5FF|grigio=E3E3E3|verde=CEF2E0|viola=EAEAFF|arancione=FFE9D2|rosso=FFD1D1|FFE9D2}}; height:8px; border:1px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|FFBC79}}; border-right:2px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|FFBC79}}; border-left:2px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|FFBC79}}" | &lt;div style="font-size:0"&gt;[[File:pix.gif|1px]]&lt;/div&gt;
|}&lt;noinclude&gt;
{{Documentation}}&lt;/noinclude&gt;</text>
    <sha1>cbf5ed0933ca88b3af094b63574c28917ef468c0</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Box-round</title>
  <ns>10</ns>
  <id>125</id>
  <revision>
    <id>295</id>
    <timestamp>2012-03-13T18:21:11Z</timestamp>
    <contributor>
      <username>SPQRobin</username>
      <id>0</id>
    </contributor>
    <comment>we like i18n</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1414" xml:space="preserve">__NOEDITSECTION__ __NOTOC__&lt;div style="clear: both;"&gt;&lt;/div&gt; 
&lt;div style="border: 1px solid {{{border|#99c}}};&lt;!--
         --&gt;background: {{{titlebackground|#ccf}}};&lt;!--
         --&gt;color: {{{titleforeground|#000}}};&lt;!--
         --&gt;padding: .1em;&lt;!--
         --&gt;text-align: center;&lt;!--
         --&gt;font-weight: bold;&lt;!--
         --&gt;font-size: 100%;&lt;!--
         --&gt;margin-bottom: 0px;&lt;!--
         --&gt;border-bottom: none;&lt;!--
         --&gt;{{border-radius|1.5em 1.5em 0 0}}&lt;!--
         --&gt;{{{titlestyle|}}};"&gt;&lt;!--
  --&gt;&lt;span class="plainlinks" &lt;!-- EDIT LINK PARAMETERS
        --&gt;style="float:right;&lt;!--
              --&gt;margin-bottom:.1em;&lt;!--
              --&gt;font-size: 80%;&lt;!--
              --&gt;padding-right: 0.5em;"&gt;&lt;!--
        --&gt;&lt;font color="{{{titleforeground|#000000}}}"&gt;[{{fullurl:{{{editpage|{{FULLPAGENAME}}}}}|action=edit}} {{int:editsection}}]&lt;/font&gt;&amp;nbsp;&lt;!--
  --&gt;&lt;/span &gt;&lt;!--
  --&gt;&lt;h2 style="font-size:100%;font-weight:bold;border: none; margin: 0; padding:0; padding-bottom:.1em;"&gt;&lt;font color="{{{titleforeground|#000000}}}"&gt;{{{title}}}&lt;/font&gt;&lt;/h2&gt;&lt;/div&gt;
&lt;div style="display: block; border: 1px solid {{{border|#99c}}}; vertical-align: top; background: {{{background|#fff}}}; color: {{{foreground|#000}}}; margin-bottom: 10px; padding: .8em 1em 1em 1.3em; margin-top: 0em; {{border-radius|0 0 1.5em 1.5em}} {{{style|}}};"&gt;{{{1|{{{text|{{{content}}}}}}}}}&lt;/div&gt;
&lt;noinclude&gt;{{doc}}&lt;/noinclude&gt;</text>
    <sha1>1dcefd534a80e840f0eeb69bfa4b352fd3d0b1d5</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:CompactTOC8</title>
  <ns>10</ns>
  <id>119</id>
  <revision>
    <id>281</id>
    <timestamp>2012-04-01T10:05:30Z</timestamp>
    <contributor>
      <username>Abani79</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>+lang tmp</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8428" xml:space="preserve">{|&lt;!--=======================================================
    --  Template CompactTOC8 -  (see NOTES at bottom)
    --=======================================================
--
--&gt; id="toc" class="toc" summary="Contents" {{
&lt;!-- ----------------------------------- Check center/right--&gt;
#ifeq:{{{center|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|align="center"|}}{{#ifeq:{{{right|}}}|yes|align="right"|}}
{{       &lt;!--see NOTE I3 below--&gt;
&lt;!-- ----------------------------------- Check name/side--&gt;
#ifeq:{{{name|}}}|no||! {{{name|{{MediaWiki:Toc}}}}}{{#ifeq:{{{side|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|&amp;#58;|}}
{{#ifeq:{{{side|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|{{!}}|{{!}}-}}}}
|{{#ifeq:{{{nobreak|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes||&lt;div style="text-align:{{{align|left}}};"&gt;}}{{
&lt;!-- --------------------------------------- Check top --&gt;
#ifeq:{{{top|}}}|yes|[[#top{{!}}Top]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
&lt;!-- --------------------------------------- Prefix headers--
          (see NOTE P2 below) --&gt;
#if:{{{pre1|{{{preSec1|}}}}}}|[[{{{pre1link|{{{preSec1link|#{{{pre1|{{{preSec1|}}}}}}}}}}}}{{!}}{{{pre1name|{{{preSec1name|{{{pre1|{{{preSec1|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre2|{{{preSec2|}}}}}}|[[{{{pre2link|{{{preSec2link|#{{{pre2|{{{preSec2|}}}}}}}}}}}}{{!}}{{{pre2name|{{{preSec2name|{{{pre2|{{{preSec2|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre3|{{{preSec3|}}}}}}|[[{{{pre3link|{{{preSec3link|#{{{pre3|{{{preSec3|}}}}}}}}}}}}{{!}}{{{pre3name|{{{preSec3name|{{{pre3|{{{preSec3|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre4|{{{preSec4|}}}}}}|[[{{{pre4link|{{{preSec4link|#{{{pre4|{{{preSec4|}}}}}}}}}}}}{{!}}{{{pre4name|{{{preSec4name|{{{pre4|{{{preSec4|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre5|{{{preSec5|}}}}}}|[[{{{pre5link|{{{preSec5link|#{{{pre5|{{{preSec5|}}}}}}}}}}}}{{!}}{{{pre5name|{{{preSec5name|{{{pre5|{{{preSec5|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre6|{{{preSec6|}}}}}}|[[{{{pre6link|{{{preSec6link|#{{{pre6|{{{preSec6|}}}}}}}}}}}}{{!}}{{{pre6name|{{{preSec6name|{{{pre6|{{{preSec6|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre7|{{{preSec7|}}}}}}|[[{{{pre7link|{{{preSec7link|#{{{pre7|{{{preSec7|}}}}}}}}}}}}{{!}}{{{pre7name|{{{preSec7name|{{{pre7|{{{preSec7|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre8|{{{preSec8|}}}}}}|[[{{{pre8link|{{{preSec8link|#{{{pre8|{{{preSec8|}}}}}}}}}}}}{{!}}{{{pre8name|{{{preSec8name|{{{pre8|{{{preSec8|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
&lt;!-- --------------------------------------- Check prebreak--&gt;
#if:{{{prebreak|}}}|{{{prebreak}}}}} {{
&lt;!-- --------------------------------------- Check symbols --&gt;
#ifeq:{{{sym|}}}|yes|[[#!$@|!$@]]|}} {{
&lt;!-- --------------------------------------- Check numbers --&gt;
#ifeq:{{{num|}}}|yes|[[#0–9|0–9]]|}} {{#ifeq:{{{symnum|}}}|yes|[[#!–9|!–9]]|
&lt;!-- --------------------------------------- List letters --&gt;
}} {{{a|[[#A|A]]}}} {{{b|[[#B|B]]}}} {{{c|[[#C|C]]}}} {{{d|[[#D|D]]}}} {{{e|[[#E|E]]}}} {{{f|[[#F|F]]}}} {{{g|[[#G|G]]}}} {{{h|[[#H|H]]}}} {{{i|[[#I|I]]}}} {{{j|[[#J|J]]}}} {{{k|[[#K|K]]}}} {{{l|[[#L|L]]}}} {{{m|[[#M|M]]}}} {{{n|[[#N|N]]}}} {{{o|[[#O|O]]}}} {{{p|[[#P|P]]}}} {{{q|[[#Q|Q]]}}} {{{r|[[#R|R]]}}} {{{s|[[#S|S]]}}} {{{t|[[#T|T]]}}} {{{u|[[#U|U]]}}} {{{v|[[#V|V]]}}} {{{w|[[#W|W]]}}} {{{x|[[#X|X]]}}} {{{y|[[#Y|Y]]}}} {{{z|[[#Z|Z]]}}} {{#ifeq:{{{nobreak|{{#ifeq:{{{1}}}|short1|yes|}}}}}|yes|&amp;nbsp;|&lt;br /&gt;}}{{
&lt;!-- ------------------------------ Check after-header1 -
          (see NOTE C2 below) --&gt;
#if:{{{custom1|{{{Sec1|}}}}}}|[[{{{custom1link|{{{Sec1link|#{{{custom1|{{{Sec1|}}}}}}}}}}}}{{!}}{{{custom1name|{{{Sec1name|{{{custom1|{{{Sec1|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
&lt;!-- ------------------------------ Check after-header2...--&gt;
#if:{{{custom2|{{{Sec2|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom2link|{{{Sec2link|#{{{custom2|{{{Sec2|}}}}}}}}}}}}{{!}}{{{custom2name|{{{Sec2name|{{{custom2|{{{Sec2|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom3|{{{Sec3|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom3link|{{{Sec3link|#{{{custom3|{{{Sec3|}}}}}}}}}}}}{{!}}{{{custom3name|{{{Sec3name|{{{custom3|{{{Sec3|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom4|{{{Sec4|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom4link|{{{Sec4link|#{{{custom4|{{{Sec4|}}}}}}}}}}}}{{!}}{{{custom4name|{{{Sec4name|{{{custom4|{{{Sec4|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom5|{{{Sec5|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom5link|{{{Sec5link|#{{{custom5|{{{Sec5|}}}}}}}}}}}}{{!}}{{{custom5name|{{{Sec5name|{{{custom5|{{{Sec5|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom6|{{{Sec6|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom6link|{{{Sec6link|#{{{custom6|{{{Sec6|}}}}}}}}}}}}{{!}}{{{custom6name|{{{Sec6name|{{{custom6|{{{Sec6|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom7|{{{Sec7|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom7link|{{{Sec7link|#{{{custom7|{{{Sec7|}}}}}}}}}}}}{{!}}{{{custom7name|{{{Sec7name|{{{custom7|{{{Sec7|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom8|{{{Sec8|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom8link|{{{Sec8link|#{{{custom8|{{{Sec8|}}}}}}}}}}}}{{!}}{{{custom8name|{{{Sec8name|{{{custom8|{{{Sec8|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Check seealso--&gt;
#ifeq:{{{seealso|}}}|yes|{{{sep|&amp;nbsp;}}} [[#See also{{!}}See also]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Check notesfirst--&gt;
#ifeq:{{{notesfirst|}}}|yes|{{{sep|&amp;nbsp;}}} [[#Notes{{!}}Notes]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Check refs--&gt;
#ifeq:{{{refs|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|{{{sep|&amp;nbsp;}}} [[#References{{!}}References]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Check notes--&gt;
#ifeq:{{{notes|}}}|yes|{{{sep|&amp;nbsp;}}} [[#Notes{{!}}Notes]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Further reading--&gt;
#ifeq:{{{further|}}}|yes|{{{sep|&amp;nbsp;}}} [[#Further reading{{!}}Further reading]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Check extlinks--&gt;
#ifeq:{{{extlinks|}}}|yes|{{{sep|&amp;nbsp;}}} [[#External links{{!}}External links]]|}}{{
&lt;!-- ================================== Check invalid words--&gt;
#ifeq:{{{break|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "break" - try "nobreak=yes".
}}{{#ifeq:{{{centre|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "centre" - try "center=yes".
}}{{#ifeq:{{{Top|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "Top" - try lowercase "top=yes".
}}{{#ifeq:{{{ref|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "ref" - try "refs=yes".
}}{{#ifeq:{{{Ref|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "Ref" - try lowercase "refs=yes".
}}{{#ifeq:{{{note|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "note" - try "note'''s'''=yes".
}}{{#ifeq:{{{ext|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "ext" - try "extlinks=yes".
}}{{#ifeq:{{{extlink|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "extlink" - try "extlinks=yes".
}}&lt;/div&gt;
|}__NOTOC__&lt;noinclude&gt;

{{documentation}}
&lt;!--PLEASE ADD CATEGORIES &amp; INTERWIKIS TO /doc PAGE, THANKS--&gt;
&lt;!--
--       -------------------------------------------------
--NOTES:
--
-- NOTE C2: Parameter "custom1=zzz" or "Sec1=zzz" shows first
--          subheader "zzz" after the "0-9 A B C D...".
--
-- NOTE I3: If-statements can be indented by leaving "{{" at
--          end of previous line and put "#if:" on next line;
--          otherwise indented lines become quote-boxes.
--
-- NOTE P2: Parameter "pre1=xxx" shows first subheader "xxx"
--          before the condensed "0-9 A B C..." appears.
--
-- NOTE S2: Parameter "sep=&amp;middot;" defines the separator
--          string displayed between subheaders (not letters).
--          It defaults to a single space, "sep=&amp;nbsp;".
--
-- NOTE V9: Coded for MediaWiki language 1.11.1 (Jan.2008);
--          wiki-format now omits HTML comments on web xfer.
--HISTORY:
-- 10Jan09 Added parameters: sep=&amp;middot; and prebreak=&lt;br&gt;.
-- 10Jan09 Added parameters: 3 more custom6, custom7, custom8.
-- 10Jan09 Added parameters: 3 more custom6link...custom8link.
-- 10Jan09 Added parameters: 3 more custom6name...custom8name.
-- 10Jan09 Added parameters: pre1, pre2, pre3... pre7, pre8.
-- 10Jan09 Added parameters: pre1link, pre2link ... pre8link.
-- 10Jan09 Added parameters: pre1name, pre2name ... pre8name.
-- 10Jan09 Added parameters: preSec1, preSec2, ... preSec8.
-- 10Jan09 Spot invalid keywords: Top/ref/Ref/note/ext etc.
-- 10Jan09 Added NOTES comments to explain template coding.
-- 10Jan09 Added HISTORY comments to log major changes.
-- 01Jul11 Added Further reading
-- [These comment lines are omitted before Internet transfer.]
--
--End Template:CompactTOC8--&gt;
{{Languages}}
&lt;/noinclude&gt;</text>
    <sha1>19bf5d824ad4f112de95d6e7d3418e8e479dec71</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:S</title>
  <ns>10</ns>
  <id>106</id>
  <revision>
    <id>253</id>
    <timestamp>2012-07-09T21:02:48Z</timestamp>
    <contributor>
      <username>Waldir</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="179" xml:space="preserve">&lt;span style="text-decoration:line-through; color:#999"&gt;{{{1|striked text}}}&lt;/span&gt;&lt;noinclude&gt;

* See also: {{tl|grey}}

[[Category:Formatting templates|{{PAGENAME}}]]
&lt;/noinclude&gt;</text>
    <sha1>8e444119abfd7aa3c1cdc49424b59145293dabd4</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Transclude</title>
  <ns>10</ns>
  <id>122</id>
  <revision>
    <id>289</id>
    <timestamp>2012-08-22T05:18:30Z</timestamp>
    <contributor>
      <username>Shanmugamp7</username>
      <id>0</id>
    </contributor>
    <comment>Reverted 1 edit by [[Special:Contributions/76.125.160.41|76.125.160.41]] ([[User talk:76.125.160.41|talk]]). ([[w:WP:TW|TW]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="400" xml:space="preserve">{{#switch: {{NAMESPACE: {{{1}}} }}
 |#default = {{FULLPAGENAME: {{{1}}} }} &lt;!-- eg "User:Foo" --&gt;
 |{{ns:0}} = 
    {{#ifeq: {{NAMESPACE: {{{1}}} }} | {{NAMESPACE: Template{{{1}}} }}
      | Template:{{{1}}}            &lt;!-- no leading colon, eg "Foo" --&gt;
      | {{PAGENAME: {{{1}}} }}      &lt;!-- leading colon, eg ":Foo", so we want the article --&gt;
    }}
}}&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>d0239e71e5745cd0d4efd032cee07341e111376b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Red</title>
  <ns>10</ns>
  <id>108</id>
  <revision>
    <id>257</id>
    <timestamp>2012-11-12T14:51:16Z</timestamp>
    <contributor>
      <username>130.209.6.41</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="113" xml:space="preserve">&lt;span style="color:#BA0000"&gt;{{{1}}}&lt;/span&gt;&lt;noinclude&gt;
[[Category:Formatting templates|{{PAGENAME}}]]
&lt;/noinclude&gt;</text>
    <sha1>679ceced3c067adf7b211de86ff810db7cd49c55</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Rellink</title>
  <ns>10</ns>
  <id>120</id>
  <revision>
    <id>283</id>
    <timestamp>2013-06-22T06:36:08Z</timestamp>
    <contributor>
      <username>Krinkle</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155" xml:space="preserve">&lt;div class="rellink mw-tpl-rellink{{#if:{{{extraclasses|}}}|&lt;nowiki&gt; &lt;/nowiki&gt;{{{extraclasses}}}}}"&gt;{{{1}}}&lt;/div&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>eb9f18d0972fa390e07dd7bbb6db1cd7ac44d352</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Tab</title>
  <ns>10</ns>
  <id>118</id>
  <revision>
    <id>279</id>
    <timestamp>2014-04-06T14:09:28Z</timestamp>
    <contributor>
      <username>86.135.248.121</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1376" xml:space="preserve">&lt;includeonly&gt;{{#if:{{{preums|}}}||&lt;td style="width: {{#if:{{{tab spacing percent|}}}|{{{tab spacing percent}}}|2}}%; border-bottom: {{#if:{{{border|}}}|{{{border}}}|solid 1px #a3b1bf}}"&gt;{{#if:{{{tab spacing percent|}}}||&amp;nbsp;}}&lt;/td&gt;}}&lt;td style="text-align: {{#if:{{{tab alignment|}}}|{{{tab alignment}}}|center}}; {{#if:{{{rounding|}}}|{{border-radius|{{{rounding}}} {{{rounding}}} 0 0}}}} padding:0.3em; border: {{#if:{{{border|}}}|{{{border}}}|solid 1px #a3b1bf}}; font-size: {{#if:{{{font-size|}}}|{{{font-size}}}|110%}}; {{#switch:{{FULLPAGENAME}}|{{{link}}}|{{{link2}}}|{{{link3}}}|{{{link4}}}|{{{link5}}}=background-color: {{#if:{{{on tab color|}}}|{{{on tab color}}}|transparent}}; border-bottom: none; font-weight:bold; |#default=background-color: {{#if:{{{off tab color|}}}|{{{off tab color}}}|#CEE0F2}}; }} {{#ifeq:{{lc:{{{nowrap|}}}}}|yes|white-space: nowrap;}}" width="{{#expr:(100/{{Number of defined parameters|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|{{{5}}}|{{{6}}}|{{{7}}}|{{{8}}}|{{{9}}}|{{{10}}}|{{{11}}}|{{{12}}}|{{{13}}}|{{{14}}}|{{{15}}}|{{{16}}}|{{{17}}}|{{{18}}}|{{{19}}}|{{{20}}}}})-{{#if:{{{tab spacing percent|}}}|{{{tab spacing percent}}}|2}}}}%"&gt;{{#if:{{{image|}}}|[[file:{{{image}}}|20px|{{{tab}}}|link={{{link|}}}]]&amp;nbsp;}}{{#ifeq:{{lc:{{{freeform|}}}}}|yes|{{{tab}}}|[[{{{link}}}|{{{tab}}}]]}}&lt;/td&gt;&lt;/includeonly&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>d7e78c5489777e489ec4a0320f35ec9c30b7c32e</sha1>
  </revision>
  <revision>
    <id>606</id>
    <parentid>280</parentid>
    <timestamp>2015-01-29T21:46:23Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="189" xml:space="preserve">&lt;includeonly&gt;&lt;div class="section"&gt;&lt;p class="title" style="font-size:small" data-section-title&gt;{{{1}}} {{{2}}}&lt;/p&gt;
&lt;div class="content" data-section-content&gt;{{{3}}}&lt;/div&gt;&lt;/div&gt;&lt;/includeonly&gt;</text>
    <sha1>bdbac5aa417cf964d37b3fe12d9bee93ee704407</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Start tab</title>
  <ns>10</ns>
  <id>116</id>
  <revision>
    <id>275</id>
    <timestamp>2014-04-06T14:12:39Z</timestamp>
    <contributor>
      <username>86.135.248.121</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15216" xml:space="preserve">&lt;includeonly&gt;&lt;!--
  --&gt;&lt;table width="100%" cellspacing=0 cellpadding=0 valign="top" border=0 style="background-color: transparent"&gt;&lt;!--
    --&gt;&lt;tr&gt;&lt;!--
--&gt;{{dummytab|border={{{border|}}}|tab spacing percent={{{tab spacing percent|}}}}}&lt;!--


--&gt;{{#if:{{{tab-1|}}}|{{tab|freeform={{{freeform-1|}}}|link={{{link-1}}}|link2={{{link2-1}}}|link3={{{link3-1}}}|link4={{{link4-1}}}|link5={{{link5-1}}}|tab={{{tab-1}}}|image={{{image-1|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-1|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}|preums=1}}}}&lt;!--


--&gt;{{#if:{{{tab-2|}}}|{{tab|freeform={{{freeform-2|}}}|link={{{link-2}}}|link2={{{link2-2}}}|link3={{{link3-2}}}|link4={{{link4-2}}}|link5={{{link5-2}}}|tab={{{tab-2}}}|image={{{image-2|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-2|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-3|}}}|{{tab|freeform={{{freeform-3|}}}|link={{{link-3}}}|link2={{{link2-3}}}|link3={{{link3-3}}}|link4={{{link4-3}}}|link5={{{link5-3}}}|tab={{{tab-3}}}|image={{{image-3|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-3|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-4|}}}|{{tab|freeform={{{freeform-4|}}}|link={{{link-4}}}|link2={{{link2-4}}}|link3={{{link3-4}}}|link4={{{link4-4}}}|link5={{{link5-4}}}|tab={{{tab-4}}}|image={{{image-4|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-4|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-5|}}}|{{tab|freeform={{{freeform-5|}}}|link={{{link-5}}}|link2={{{link2-5}}}|link3={{{link3-5}}}|link4={{{link4-5}}}|link5={{{link5-5}}}|tab={{{tab-5}}}|image={{{image-5|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-5|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-6|}}}|{{tab|freeform={{{freeform-6|}}}|link={{{link-6}}}|link2={{{link2-6}}}|link3={{{link3-6}}}|link4={{{link4-6}}}|link5={{{link5-6}}}|tab={{{tab-6}}}|image={{{image-6|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-6|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-7|}}}|{{tab|freeform={{{freeform-7|}}}|link={{{link-7}}}|link2={{{link2-7}}}|link3={{{link3-7}}}|link4={{{link4-7}}}|link5={{{link5-7}}}|tab={{{tab-7}}}|image={{{image-7|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-7|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-8|}}}|{{tab|freeform={{{freeform-8|}}}|link={{{link-8}}}|link2={{{link2-8}}}|link3={{{link3-8}}}|link4={{{link4-8}}}|link5={{{link5-8}}}|tab={{{tab-8}}}|image={{{image-8|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-8|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-9|}}}|{{tab|freeform={{{freeform-9|}}}|link={{{link-9}}}|link2={{{link2-9}}}|link3={{{link3-9}}}|link4={{{link4-9}}}|link5={{{link5-9}}}|tab={{{tab-9}}}|image={{{image-9|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-9|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-10|}}}|{{tab|freeform={{{freeform-10|}}}|link={{{link-10}}}|link2={{{link2-10}}}|link3={{{link3-10}}}|link4={{{link4-10}}}|link5={{{link5-10}}}|tab={{{tab-10}}}|image={{{image-10|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-10|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-11|}}}|{{tab|freeform={{{freeform-11|}}}|link={{{link-11}}}|link2={{{link2-11}}}|link3={{{link3-11}}}|link4={{{link4-11}}}|link5={{{link5-11}}}|tab={{{tab-11}}}|image={{{image-11|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-1|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-12|}}}|{{tab|freeform={{{freeform-12|}}}|link={{{link-12}}}|link2={{{link2-12}}}|link3={{{link3-12}}}|link4={{{link4-12}}}|link5={{{link5-12}}}|tab={{{tab-12}}}|image={{{image-12|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-2|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-13|}}}|{{tab|freeform={{{freeform-13|}}}|link={{{link-13}}}|link2={{{link2-13}}}|link3={{{link3-13}}}|link4={{{link4-13}}}|link5={{{link5-13}}}|tab={{{tab-13}}}|image={{{image-13|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-3|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-14|}}}|{{tab|freeform={{{freeform-14|}}}|link={{{link-14}}}|link2={{{link2-14}}}|link3={{{link3-14}}}|link4={{{link4-14}}}|link5={{{link5-14}}}|tab={{{tab-14}}}|image={{{image-14|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-4|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-15|}}}|{{tab|freeform={{{freeform-15|}}}|link={{{link-15}}}|link2={{{link2-15}}}|link3={{{link3-15}}}|link4={{{link4-15}}}|link5={{{link5-15}}}|tab={{{tab-15}}}|image={{{image-15|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-5|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-16|}}}|{{tab|freeform={{{freeform-16|}}}|link={{{link-16}}}|link2={{{link2-16}}}|link3={{{link3-16}}}|link4={{{link4-16}}}|link5={{{link5-16}}}|tab={{{tab-16}}}|image={{{image-16|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-6|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-17|}}}|{{tab|freeform={{{freeform-17|}}}|link={{{link-17}}}|link2={{{link2-17}}}|link3={{{link3-17}}}|link4={{{link4-17}}}|link5={{{link5-17}}}|tab={{{tab-17}}}|image={{{image-17|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-7|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-18|}}}|{{tab|freeform={{{freeform-18|}}}|link={{{link-18}}}|link2={{{link2-18}}}|link3={{{link3-18}}}|link4={{{link4-18}}}|link5={{{link5-18}}}|tab={{{tab-18}}}|image={{{image-18|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-8|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-19|}}}|{{tab|freeform={{{freeform-19|}}}|link={{{link-19}}}|link2={{{link2-19}}}|link3={{{link3-19}}}|link4={{{link4-19}}}|link5={{{link5-19}}}|tab={{{tab-19}}}|image={{{image-19|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-9|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-20|}}}|{{tab|freeform={{{freeform-20|}}}|link={{{link-20}}}|link2={{{link2-20}}}|link3={{{link3-20}}}|link4={{{link4-20}}}|link5={{{link5-20}}}|tab={{{tab-20}}}|image={{{image-20|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-10|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{dummytab|border={{{border|}}}|tab spacing percent={{{tab spacing percent|}}}}}&lt;!--
--&gt;&lt;/tr&gt;&lt;!--
 --&gt;&lt;/table&gt;&lt;!--
 --&gt;{{#ifeq:{{{frame|}}}|yes|&lt;div style="border: {{{border|solid 1px #a3b1bf}}}; padding: .5em 1em 1em 1em; border-top: none; background-color: {{{frame color|{{{on tab color|transparent}}}}}}; color: black; zoom: 1"&gt;&lt;!--
   --&gt;&lt;div style="padding: 1ex"&gt;}}&lt;!--
--&gt;&lt;/includeonly&gt;&lt;!--
--&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>e76d923db135374f739db247717039ec4e689162</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:End tab</title>
  <ns>10</ns>
  <id>117</id>
  <revision>
    <id>277</id>
    <timestamp>2014-04-06T14:15:58Z</timestamp>
    <contributor>
      <username>86.135.248.121</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1590" xml:space="preserve">&lt;div&gt;&lt;includeonly&gt;&lt;!--

--&gt;{{clear}}&lt;/div&gt;&lt;!--
--&gt;{{#if:{{{URL-1|}}}|&lt;div style="float:right; margin-top: 0.0em; margin-bottom:3px; background-color: {{{Off tab color|#cee0f2}}}; padding: .2em .6em; font-size: 130%; border: {{{border|1px solid #a3b1bf}}}; {{#if:{{{rounding|}}}|-moz-border-radius: {{{rounding}}} {{{rounding}}} 0 0; border-radius: {{{rounding}}} {{{rounding}}} 0 0;}}"&gt; Next page : {{#switch:{{FULLPAGENAME}}|
{{{URL-1}}}=[[{{{URL-2|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-2|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-2}}}=[[{{{URL-3|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-3|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-3}}}=[[{{{URL-4|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-4|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-4}}}=[[{{{URL-5|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-5|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-5}}}=[[{{{URL-6|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-6|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-6}}}=[[{{{URL-7|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-7|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-7}}}=[[{{{URL-8|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-8|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-8}}}=[[{{{URL-9|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-9|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-9}}}=[[{{{URL-10|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-10|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-10}}}=[[{{{URL-End|{{{URL-1}}}}}}|'''{{{Tab-End|{{{Tab-1}}}}}}''']]|
}}&lt;span style="font-size: larger; font-weight: bold;"&gt;&amp;rarr;&lt;/span&gt;&lt;!--
--&gt;&lt;div style="clear:both"&gt;&lt;/div&gt;&lt;/div&gt;|&lt;div style="clear:both"&gt;&lt;/div&gt;}}&lt;/div&gt;&lt;/includeonly&gt;&lt;noinclude&gt;{{doc}}&lt;/noinclude&gt;</text>
    <sha1>d76a781f167cc46cbbe3bf964b551218821e865e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Collapse bottom</title>
  <ns>10</ns>
  <id>111</id>
  <revision>
    <id>265</id>
    <timestamp>2014-06-02T01:57:11Z</timestamp>
    <contributor>
      <username>Shirayuki</username>
      <id>0</id>
    </contributor>
    <comment>{{TNT|Documentation}}</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">|}&lt;/div&gt;&lt;noinclude&gt;
{{TNT|Documentation}}
&lt;!-- PLEASE ADD THIS TEMPLATE'S CATEGORIES AND INTERWIKIS TO THE /doc SUBPAGE, THANKS --&gt;
&lt;/noinclude&gt;</text>
    <sha1>3e150427ef410d88db3ed21c0539f3e90ee3faab</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Tab/sandbox</title>
  <ns>10</ns>
  <id>126</id>
  <revision>
    <id>297</id>
    <timestamp>2014-08-13T15:39:33Z</timestamp>
    <contributor>
      <username>Jackmcbarn</username>
      <id>0</id>
    </contributor>
    <comment>mirror from [[Template:Tab]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1376" xml:space="preserve">&lt;includeonly&gt;{{#if:{{{preums|}}}||&lt;td style="width: {{#if:{{{tab spacing percent|}}}|{{{tab spacing percent}}}|2}}%; border-bottom: {{#if:{{{border|}}}|{{{border}}}|solid 1px #a3b1bf}}"&gt;{{#if:{{{tab spacing percent|}}}||&amp;nbsp;}}&lt;/td&gt;}}&lt;td style="text-align: {{#if:{{{tab alignment|}}}|{{{tab alignment}}}|center}}; {{#if:{{{rounding|}}}|{{border-radius|{{{rounding}}} {{{rounding}}} 0 0}}}} padding:0.3em; border: {{#if:{{{border|}}}|{{{border}}}|solid 1px #a3b1bf}}; font-size: {{#if:{{{font-size|}}}|{{{font-size}}}|110%}}; {{#switch:{{FULLPAGENAME}}|{{{link}}}|{{{link2}}}|{{{link3}}}|{{{link4}}}|{{{link5}}}=background-color: {{#if:{{{on tab color|}}}|{{{on tab color}}}|transparent}}; border-bottom: none; font-weight:bold; |#default=background-color: {{#if:{{{off tab color|}}}|{{{off tab color}}}|#CEE0F2}}; }} {{#ifeq:{{lc:{{{nowrap|}}}}}|yes|white-space: nowrap;}}" width="{{#expr:(100/{{Number of defined parameters|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|{{{5}}}|{{{6}}}|{{{7}}}|{{{8}}}|{{{9}}}|{{{10}}}|{{{11}}}|{{{12}}}|{{{13}}}|{{{14}}}|{{{15}}}|{{{16}}}|{{{17}}}|{{{18}}}|{{{19}}}|{{{20}}}}})-{{#if:{{{tab spacing percent|}}}|{{{tab spacing percent}}}|2}}}}%"&gt;{{#if:{{{image|}}}|[[file:{{{image}}}|20px|{{{tab}}}|link={{{link|}}}]]&amp;nbsp;}}{{#ifeq:{{lc:{{{freeform|}}}}}|yes|{{{tab}}}|[[{{{link}}}|{{{tab}}}]]}}&lt;/td&gt;&lt;/includeonly&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>d7e78c5489777e489ec4a0320f35ec9c30b7c32e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Uselang</title>
  <ns>10</ns>
  <id>140</id>
  <revision>
    <id>329</id>
    <timestamp>2014-08-30T14:25:25Z</timestamp>
    <contributor>
      <username>Steinsplitter</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Protected "[[Template:Uselang]]": Highly visible template: used on [[Special:MostTranscludedPages|12,027]] pages ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="138" xml:space="preserve">{{#if: {{{lang|}}} | {{{lang|}}} | {{#ifeq: {{int:Lang}} | &lt;Lang&gt; | default | {{int:Lang}} }} }}&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>297a29f24992bc20bf1a8d217933907f49e263e4</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Smallcaps</title>
  <ns>10</ns>
  <id>128</id>
  <revision>
    <id>301</id>
    <timestamp>2014-10-24T00:15:14Z</timestamp>
    <contributor>
      <username>Genium</username>
      <id>0</id>
    </contributor>
    <comment>Creating Template:Smallcaps</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="120" xml:space="preserve">&lt;includeonly&gt;&lt;span style="font-variant: small-caps"&gt;{{{1}}}&lt;/span&gt;&lt;/includeonly&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>96dbaf71349f4af78c01cfab7eaa8fd953fa7784</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:TNTN</title>
  <ns>10</ns>
  <id>81</id>
  <revision>
    <id>333</id>
    <parentid>219</parentid>
    <timestamp>2014-10-26T15:26:18Z</timestamp>
    <contributor>
      <username>Steinsplitter</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Protected "[[Template:TNTN]]": Highly visible template ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="49" xml:space="preserve">#REDIRECT [[Template:Translatable template name]]</text>
    <sha1>51aba18c9e7edde0de5272258792895d16b983c2</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Documentation/sandbox</title>
  <ns>10</ns>
  <id>124</id>
  <revision>
    <id>293</id>
    <timestamp>2014-10-29T17:15:03Z</timestamp>
    <contributor>
      <username>151.225.136.51</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="182" xml:space="preserve">{{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}&lt;noinclude&gt;
&lt;!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --&gt;
&lt;/noinclude&gt;</text>
    <sha1>ce7fd93f18c46b4fa871bf679afd05cbda72d8c4</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Grey</title>
  <ns>10</ns>
  <id>101</id>
  <revision>
    <id>243</id>
    <timestamp>2014-11-19T14:44:26Z</timestamp>
    <contributor>
      <username>André Costa (WMSE)</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Repairing</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="390" xml:space="preserve">&lt;span style="color:#999;"&gt;{{{1}}}&lt;/span&gt;&lt;noinclude&gt;

* See also: {{tl|s}}

[[Category:Formatting templates|{{PAGENAME}}]]

&lt;templatedata&gt;
{
	"description": "Display text in gray",
	"params": {
		"1": {
			"label": "Text",
			"description": "Text to be displayed",
			"type": "string",
			"default": "text",
			"suggested": true,
			"autovalue": "value"
		}
	}
}
&lt;/templatedata&gt;
&lt;/noinclude&gt;</text>
    <sha1>629dd57a007f80942599a00e027948fcedfcb97c</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Languages/Lang</title>
  <ns>10</ns>
  <id>135</id>
  <revision>
    <id>319</id>
    <timestamp>2014-12-15T17:35:20Z</timestamp>
    <contributor>
      <username>Gqqnb</username>
      <id>0</id>
    </contributor>
    <comment>remove useless &lt;includeonly&gt;</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="299" xml:space="preserve">{{#ifexist: {{#if:{{{2|}}}|{{{2}}}|{{NAMESPACE}}:{{BASEPAGENAME}}}}/{{{1|}}}
|&amp;nbsp;• &lt;bdi lang="{{{1|}}}"&gt;{{#if:{{{2|}}}
  |[[:{{{2|}}}/{{{1|}}}|{{#language:{{{1|}}}}}]]
  |[[:{{NAMESPACE}}:{{BASEPAGENAME}}/{{{1|}}}|{{#language:{{{1|}}}}}]]
  }}&lt;/bdi&gt;
}}&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>c21fa44889712c6aa27a79bb3191f2f6e29563f4</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Languages/Title</title>
  <ns>10</ns>
  <id>136</id>
  <revision>
    <id>321</id>
    <timestamp>2014-12-15T17:45:23Z</timestamp>
    <contributor>
      <username>Gqqnb</username>
      <id>0</id>
    </contributor>
    <comment>zh=語言:，what the hell only 語?</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3087" xml:space="preserve">{{LangSwitch|lang={{{1|}}}
|default=Language:
|Languages=Languages:
|MediaWiki=Languages:
|af=Taal:
|aln=Gjuha:
|am=ቋምቋ፦
|an=Idioma:
|ang=Sprǣc:
|ar=:اللغة
|arc=ܠܫܢܐ:
|arn=Dungun:
|arz=:اللغة
|as=ভাষা:
|ast=Llingua:
|avk=Ava:
|ay=Aru:
|az=Dil:
|bat-smg=Kalba:
|bcc=زبان:
|bcl=Tataramon:
|be=Мова:
|be-tarask=Мова:
|bg=Език:
|bn=ভাষা:
|br=Yezh :
|bs=Jezik:
|ca=Llengua :
|cdo=Ngṳ̄-ngiòng:
|ce=Мотт:
|ceb=Pinulongan:
|ch=Lengguahe:
|ckb-arab=زمان:
|co=Lingua :
|crh-cyrl=Тиль:
|crh-latn=Til:
|cs=Jazyk:
|cu=ѩꙁꙑ́къ :
|cv=Чĕлхе:
|cy=Iaith:
|da=Sprog:
|de=Sprache:
|diq=Zıwan:
|dsb=Rěc:
|ee=Gbe:
|el=Γλώσσα:
|en=Language:
|eo=Lingvo:
|es=Idioma:
|et=Keel:
|eu=Hizkuntza:
|ext=Palra:
|fa=زبان:
|fi=Kieli:
|fo=Mál:
|fr=Langue :
|frc=Langue :
|frp=Lengoua :
|fur=Lenghe :
|fy=Taal:
|ga=Teanga:
|gag=Dil:
|gan-hans=语言:
|gan-hant=語言:
|gl=Lingua:
|gn=Ñe'ẽ:
|got=Razda:
|grc=Γλῶσσα:
|gsw=Sproch:
|gu=ભાષા:
|gv=Çhengey:
|hak=Ngî-ngièn:
|haw=Kou 'ōlelo:
|he=שפה:
|hi=भाषा:
|hif-latn=Bhasa:
|hr=Jezik:
|hsb=Rěč:
|ht=Lang:
|hu=Nyelv:
|hy=Լեզու.
|ia=Lingua:
|id=Bahasa:
|ie=Lingue:
|ilo=Lengguahe:
|io=Linguo:
|is=Tungumál:
|it=Lingua:
|ja=言語:
|jv=Basa:
|ka=ენა:
|kaa=Til:
|kab=Tutlayt:
|kg=Ndinga:
|kiu=Zon:
|kk-arab=:ٴتىل
|kk-cyrl=Тіл:
|kk-latn=Til:
|km=ភាសា៖
|kn=ಭಾಷೆ:
|ko=언어:
|ksh=Sproch:
|ku-latn=Ziman:
|kv=Кыв:
|kw=Yeth:
|ky=Тил:
|la=Lingua:
|lb=Sprooch:
|lfn=Lingua:
|li=Taol:
|lij=Lengoa:
|loz=Zwa Siselect:
|lt=Kalba:
|lv=Valoda:
|lzh=語：
|mdf=Кяль:
|mg=fiteny:
|mhr=Йылме:
|min=Bahaso:
|mk=Јазик:
|ml=ഭാഷ:
|mn=Хэл:
|mr=भाषा:
|ms=Bahasa:
|mt=Lingwa:
|mwl=Lhéngua:
|my=ဘာသာ:
|myv=Кель:
|nah=Tlahtōlli:
|nap=Lengua:
|nds=Spraak:
|nds-nl=Taal:
|ne=भाषा:
|new=भाषा:
|nl=Taal:
|nn=Språk:
|no=Språk:
|nso=Polelo:
|oc=Lenga :
|os=Æвзаг:
|pa=ਭਾਸ਼ਾ:
|pam=Amanu:
|pdc=Schprooch:
|pdt=Sproak:
|pl=Język:
|pms=Lenga:
|pnb=بولی:
|pnt=Γλώσσαν:
|prg=Bilā:
|ps=ژبه:
|pt|pt-br=Língua:
|qu=Rimay:
|rm=Lingua:
|ro=Limba:
|roa-tara=Lénga:
|ru=Язык:
|sa=भाषा:
|sah=Омугун тыла:
|sc=Limba:
|scn=Lingua:
|sco=Leid:
|sdc=Linga:
|se=Giella:
|sei=Itom:
|sh=Jezik:
|shi=tutlayt:
|si=භාෂාව:
|sk=Jazyk:
|sl=Jezik:
|sli=Sproache:
|so=Luqada:
|sq=Gjuha:
|sr-ec=Језик:
|sr-el=Jezik:
|srn=Tongo:
|ss=Lúlwîmi:
|stq=Sproake:
|su=Basa:
|sv=Språk:
|sw=Lugha:
|szl=Godka:
|ta=மொழி:
|te=భాష:
|tet=Lian:
|tg-cyrl=Забон:
|th=ภาษา:
|ti=ቋንቋ:
|tk=Dil:
|tl=Wika:
|to=Lea:
|tr=Dil:
|tt-cyrl=Тел:
|tyv=Дыл:
|ug-arab=:تىل
|ug-latn=Til:
|uk=Мова:
|vec=Lengua:
|vep=Kel’:
|vi=Ngôn ngữ:
|vo=Pük:
|vro=Kiil:
|wa=Lingaedje:
|war=Yinaknan:
|wo=Làkk:
|wuu=语言:
|xal=Келн:
|xh=Ulwimi:
|xmf=ნინა:
|yi=שפראך:
|yo=Èdè:
|yue=語言:
|zea=Taele:
|zh=語言:
|zh-hans=语言:
|zh-hant=語言:
|zu=Ulimi:
}}&lt;noinclude&gt;{{Documentation}}&lt;/noinclude&gt;</text>
    <sha1>9a6086fadca92393091513e283c466a398fdea1d</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:LangSwitch</title>
  <ns>10</ns>
  <id>133</id>
  <revision>
    <id>315</id>
    <timestamp>2015-01-28T11:57:00Z</timestamp>
    <contributor>
      <username>176.195.109.14</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="631" xml:space="preserve">{{{ 
  {{#switch: {{{ {{Uselang|lang={{{lang|}}}}} |}}} 
  | ~ = empty
  |   = {{#switch: {{{ {{GetFallback| {{Uselang|lang={{{lang|}}}}} |default=default}} |}}}
    | ~ = empty
    |   = {{#switch: {{{ {{GetFallback2| {{Uselang|lang={{{lang|}}}}} |default=default}} |}}}
      | ~        = empty
      |          = {{#if: {{{default|}}} | default | en }}
      | #default = {{GetFallback2| {{Uselang|lang={{{lang|}}}}} |default=default}}
      }}
    | #default = {{GetFallback| {{Uselang|lang={{{lang|}}}}} |default=default}}
    }}
  | #default = {{Uselang|lang={{{lang|}}}}}
  }} 
|}}}&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>6276da6db4a231df3efb5b4f4a68cc35dc2b8211</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:Elink</title>
  <ns>10</ns>
  <id>266</id>
  <revision>
    <id>598</id>
    <timestamp>2015-01-29T00:51:20Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="76" xml:space="preserve">&lt;includeonly&gt;&lt;span class="plainlinks"&gt;[{{{1}}} {{{2}}}]&lt;/span&gt;&lt;/includeonly&gt;</text>
    <sha1>d5574cbe6609c35f82ca56241f049a823b7fdfac</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Abstract</title>
  <ns>102</ns>
  <id>240</id>
  <revision>
    <id>538</id>
    <timestamp>2015-02-05T15:20:04Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Author</title>
  <ns>102</ns>
  <id>241</id>
  <revision>
    <id>540</id>
    <timestamp>2015-02-05T15:20:04Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Average Rating Stars</title>
  <ns>102</ns>
  <id>242</id>
  <revision>
    <id>542</id>
    <timestamp>2015-02-05T15:20:04Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Citation</title>
  <ns>102</ns>
  <id>243</id>
  <revision>
    <id>544</id>
    <timestamp>2015-02-05T15:20:04Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:DOI</title>
  <ns>102</ns>
  <id>244</id>
  <revision>
    <id>546</id>
    <timestamp>2015-02-05T15:20:04Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47" xml:space="preserve">[[Has type::Text]]
[[Category:Framework Pages]]</text>
    <sha1>793928a9cf583921e396749ebc4a0c88e2d40746</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Five Star Review Count</title>
  <ns>102</ns>
  <id>245</id>
  <revision>
    <id>548</id>
    <timestamp>2015-02-05T15:20:04Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Four Star Review Count</title>
  <ns>102</ns>
  <id>246</id>
  <revision>
    <id>550</id>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Full Title</title>
  <ns>102</ns>
  <id>49</id>
  <revision>
    <id>552</id>
    <parentid>73</parentid>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Item</title>
  <ns>102</ns>
  <id>247</id>
  <revision>
    <id>554</id>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Page]].
[[Category:Framework Pages]]</text>
    <sha1>35138e263c93432ca7be64f2ecdb8edf070d91e5</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Item Type</title>
  <ns>102</ns>
  <id>59</id>
  <revision>
    <id>556</id>
    <parentid>124</parentid>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="492" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]

[[Allows value::article]]
[[Allows value::book]]
[[Allows value::booklet]]
[[Allows value::conference]]
[[Allows value::inbook]]
[[Allows value::incollection]]
[[Allows value::inproceedings]]
[[Allows value::manual]]
[[Allows value::mastersthesis]]
[[Allows value::misc]]
[[Allows value::phdthesis]]
[[Allows value::proceedings]]
[[Allows value::standard]]
[[Allows value::techreport]]
[[Allows value::unpublished]]</text>
    <sha1>abcd7257bbc4f8f15fdc7663c0b0f654f7b111a9</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Item Type Image</title>
  <ns>102</ns>
  <id>248</id>
  <revision>
    <id>558</id>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Keyword Links</title>
  <ns>102</ns>
  <id>249</id>
  <revision>
    <id>560</id>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:One Star Review Count</title>
  <ns>102</ns>
  <id>250</id>
  <revision>
    <id>562</id>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Publisher</title>
  <ns>102</ns>
  <id>251</id>
  <revision>
    <id>564</id>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Rating</title>
  <ns>102</ns>
  <id>252</id>
  <revision>
    <id>566</id>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">This is a property of type [[Has type::Number]].
[[Category:Framework Pages]]</text>
    <sha1>58a20cb7fe63db16b7ea0e1b733e8a5bf9e55ac8</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Review Title</title>
  <ns>102</ns>
  <id>253</id>
  <revision>
    <id>568</id>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">This is a property of type [[Has type::String]].
[[Category:Framework Pages]]</text>
    <sha1>f250aed81da8f3df5d26714a915e6cee93cd086e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Reviewer</title>
  <ns>102</ns>
  <id>254</id>
  <revision>
    <id>570</id>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Page]].
[[Category:Framework Pages]]</text>
    <sha1>35138e263c93432ca7be64f2ecdb8edf070d91e5</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Sorting Title</title>
  <ns>102</ns>
  <id>255</id>
  <revision>
    <id>572</id>
    <timestamp>2015-02-05T15:20:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">This is a property of type [[Has type::String]].
[[Category:Framework Pages]]</text>
    <sha1>f250aed81da8f3df5d26714a915e6cee93cd086e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Three Star Review Count</title>
  <ns>102</ns>
  <id>256</id>
  <revision>
    <id>574</id>
    <timestamp>2015-02-05T15:20:06Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Two Star Review Count</title>
  <ns>102</ns>
  <id>257</id>
  <revision>
    <id>576</id>
    <timestamp>2015-02-05T15:20:06Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Volume</title>
  <ns>102</ns>
  <id>258</id>
  <revision>
    <id>578</id>
    <timestamp>2015-02-05T15:20:06Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Property:Year</title>
  <ns>102</ns>
  <id>259</id>
  <revision>
    <id>580</id>
    <timestamp>2015-02-05T15:20:06Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">This is a property of type [[Has type::String]].
[[Category:Framework Pages]]</text>
    <sha1>f250aed81da8f3df5d26714a915e6cee93cd086e</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Clear</title>
  <ns>10</ns>
  <id>129</id>
  <revision>
    <id>303</id>
    <timestamp>2015-02-10T18:27:06Z</timestamp>
    <contributor>
      <username>Edokter</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Protected "[[Template:Clear]]" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="81" xml:space="preserve">&lt;div style="clear:{{{1|both}}};"&gt;&lt;/div&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>38bab3e3d7fbd3d6800d46556e60bc6bac494d72</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:RefList</title>
  <ns>10</ns>
  <id>265</id>
  <revision>
    <id>596</id>
    <timestamp>2015-02-21T17:22:23Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <comment>Created page with "&lt;includeonly&gt; '''References''' &lt;div id="reference-block"&gt; &lt;references /&gt;&lt;/div&gt;&lt;/includeonly&gt;"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="92" xml:space="preserve">&lt;includeonly&gt;
'''References'''
&lt;div id="reference-block"&gt;
&lt;references /&gt;&lt;/div&gt;&lt;/includeonly&gt;</text>
    <sha1>26237a1877fd0c09294cb2c9fc083e4a7448c9c3</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:New Paragraph</title>
  <ns>10</ns>
  <id>62</id>
  <revision>
    <id>594</id>
    <parentid>132</parentid>
    <timestamp>2015-02-23T20:40:07Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="51" xml:space="preserve">&lt;includeonly&gt;
&lt;div class="np"&gt;&lt;/div&gt;
&lt;/includeonly&gt;</text>
    <sha1>26a6db7d50ee393b0d5d7e0800bd93c8d30fdd52</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Blue</title>
  <ns>10</ns>
  <id>109</id>
  <revision>
    <id>259</id>
    <timestamp>2015-02-24T03:36:29Z</timestamp>
    <contributor>
      <username>Shirayuki</username>
      <id>0</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="167" xml:space="preserve">&lt;noinclude&gt;
{{languages}}
&lt;/noinclude&gt;&lt;span style="color:#0645AD;"&gt;{{{1}}}&lt;/span&gt;&lt;noinclude&gt;
[[Category:Formatting templates{{translation}}|{{PAGENAME}}]]
&lt;/noinclude&gt;</text>
    <sha1>3300263cd97853e64e01cf269e5c1e5cde832838</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Talk:Selecting</title>
  <ns>1</ns>
  <id>228</id>
  <revision>
    <id>514</id>
    <timestamp>2015-02-24T17:18:52Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <comment>Created page with "[[Category:Page]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">[[Category:Page]]</text>
    <sha1>6d68468a3db13903a05fdaee202205a53a76ce07</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Vision</title>
  <ns>0</ns>
  <id>237</id>
  <revision>
    <id>532</id>
    <timestamp>2015-02-24T17:59:11Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <comment>Created page with "[[Category:Page]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">[[Category:Page]]</text>
    <sha1>6d68468a3db13903a05fdaee202205a53a76ce07</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Wiki Federation</title>
  <ns>0</ns>
  <id>238</id>
  <revision>
    <id>534</id>
    <timestamp>2015-02-24T17:59:30Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <comment>Created page with "[[Category:Page]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">[[Category:Page]]</text>
    <sha1>6d68468a3db13903a05fdaee202205a53a76ce07</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Download</title>
  <ns>10</ns>
  <id>268</id>
  <revision>
    <id>602</id>
    <timestamp>2015-02-25T17:22:14Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="311" xml:space="preserve">&lt;includeonly&gt;
{|
| style="width:100%;background:#eee3d0; font-weight:normal; font-size:80%;border: solid 1px #e0cdab;text-align:left; font-color:#000; padding:5px 5px;margin-bottom:-1px;"|[[Image:Download.png|36px|link=]] Download links and installation instructions may be found here: {{{1}}}
|}
&lt;/includeonly&gt;</text>
    <sha1>3a1fc8aff1d7a1df320b5a9ba2995f21b58b1568</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Gallery</title>
  <ns>10</ns>
  <id>269</id>
  <revision>
    <id>604</id>
    <timestamp>2015-02-25T20:27:14Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="220" xml:space="preserve">&lt;includeonly&gt;&lt;div style="display: inline-block;margin: 5px;"&gt;
{|
|{{#widget:LinkedIn Profile
|profile={{{2}}}
|name={{{3}}}
|norelated
}}
|-
|[[File:Gestalt Wiki Framework.png|24px|link=]] {{{1}}}
|}&lt;/div&gt;
&lt;/includeonly&gt;</text>
    <sha1>3f46729562273b5c431aef415b9292cb47da7388</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Hide All Title Icons</title>
  <ns>0</ns>
  <id>219</id>
  <revision>
    <id>496</id>
    <timestamp>2015-02-26T00:37:03Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="233" xml:space="preserve">{{Breadcrumb}}
{{#set:Hide Title Icon=all}}
{{#set:Title Icon=UnderConstruction.png}}
{{#set:Title Icon=Article.png}}
{{#set:Title Icon=Inproceedings.png}}
[[Category:Title Icon Category]]
{{#set:Name={{PAGENAME}}}}
[[Category:Page]]</text>
    <sha1>5d215b43cf5834c8198393b685fe8b7686067ccd</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Hide Page Title Icons</title>
  <ns>0</ns>
  <id>220</id>
  <revision>
    <id>498</id>
    <timestamp>2015-02-26T00:37:14Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="235" xml:space="preserve">{{Breadcrumb}}
{{#set:Hide Title Icon=page}}
{{#set:Title Icon=UnderConstruction.png}}
{{#set:Title Icon=Article.png}}
{{#set:Title Icon=Inproceedings.png}}
 [[Category:Title Icon Category]]
{{#set:Name={{PAGENAME}}}}
[[Category:Page]]</text>
    <sha1>0f8e3d0de4d9ec150e1db4be3d26bef072fb02c1</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Hide Category Title Icon</title>
  <ns>0</ns>
  <id>221</id>
  <revision>
    <id>500</id>
    <timestamp>2015-02-26T00:37:23Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="239" xml:space="preserve">{{Breadcrumb}}
{{#set:Hide Title Icon=category}}
{{#set:Title Icon=UnderConstruction.png}}
{{#set:Title Icon=Article.png}}
{{#set:Title Icon=Inproceedings.png}}
 [[Category:Title Icon Category]]
{{#set:Name={{PAGENAME}}}}
[[Category:Page]]</text>
    <sha1>617f488b4cc42ab8c47c3eb09c5e4e72a0468f80</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Nested Tabs</title>
  <ns>0</ns>
  <id>234</id>
  <revision>
    <id>526</id>
    <timestamp>2015-02-26T01:17:32Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Bclemente moved page [[Case Study]] to [[Nested Tabs]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2262" xml:space="preserve">&lt;div style="font-size:80%;"&gt;
&lt;div class="section-container auto"  data-section&gt;
&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Background&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Introduction|{{:Gestalt Wiki Framework}}}}
{{Tab||Background|{{:Background}}}}
{{Tab||Enterprise Collaboration|{{:Enterprise Collaboration}}}}
{{Tab||Content Networks|{{:Content Networks}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Wiki Design&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Wiki Development&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Configure a Wiki|[[Image:UnderConstruction.png|50px]]}} 
{{Tab||Create Classes|[[Image:UnderConstruction.png|50px]]}}  
{{Tab||Create Queries and Visualizations|[[Image:UnderConstruction.png|50px]]}}  
{{Tab||Patterns|[[Image:UnderConstruction.png|50px]]}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Gestalt Wiki Framework Extensions&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Introduction|{{:Gestalt Wiki Framework Extensions}}}}
{{Tab||Title Icon|{{:Title Icon}}}} 
{{Tab||Semantic Rating|{{:Semantic Rating}}}}  
{{Tab||VIKI Network Graph|{{:VIKI Network Graph}}}}  
{{Tab||VIKI Semantic Title|{{:VIKI Semantic Title}}}}
{{Tab||VIKI Title Icon|{{:VIKI Title Icon}}}}
{{Tab||Hierarchy Builder|{{:Hierarchy Builder}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;About&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Publications|{{:Publications}}}}
{{Tab||Team|{{:Team}}}}
{{Tab||MITRE|{{:MITRE}}}}
{{Tab||Contact|{{:Contact}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;
&lt;/div&gt;
__NOTOC__
 {{#set:Hide Title Icon=all}}</text>
    <sha1>c8a0aaf4f28e87f141edba6963927368fddb3de0</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Enterprise Collaboration</title>
  <ns>0</ns>
  <id>214</id>
  <revision>
    <id>486</id>
    <timestamp>2015-02-26T18:28:04Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2942" xml:space="preserve">{{Breadcrumb}}
&lt;div class="row" &gt;&lt;div class="large-8 columns"&gt;Traditionally, enterprise knowledge work business processes involve staff creating a document, spreadsheet, or briefing and then emailing it to a group for review. Each time the information container is emailed to an author, an additional copy of the resource is created. Multiple copies of the information container at different stages of the editing process is copied to each author's desktop, email queue, and/or shared folders. To bring all of the modifications into a single instance of the information container, authors need to accept and merge changes. When the group of authors is highly active, it can be very time-consuming to ensure that all changes are correctly considered, accepted, and merged. Searching through large email folders to find the most current version can also be time-consuming. A document management system can improve multi-author editing using a check in and check out process. However, over time, the hierarchical structure of the document management system can become saturated with so many items that authors find it difficult to navigate or find the information containers they need.&lt;/div&gt;
&lt;div class="large-4 columns"&gt;[[Image:NxNAuthoring.png|400px]]&lt;br&gt;Emailing Knowledge Resources&lt;/div&gt;&lt;/div&gt; 
&lt;div class="row" &gt;&lt;div class="large-8 columns"&gt;Collaborating on a common page or set of pages in a wiki can eliminate the version control and findability problems cited above. Instead of emailing or posting the resource to a document management system, authors use a wiki to shape the resource. All edits are logged and authors can inspect the history of the page to learn how the page has changed over time and who were the authors who made the changes. There is no need to merge edits. Merge happens each time an author edits the page. Not only can these authors inspect the page history, they can also make comments or discuss the page. A structured wiki adds support to the authoring process by ensuring that authors edit the latest version and by authors embedding queries to aggregate and filter related knowledge, and display query results as tag clouds, bar charts, network graphs, faceted navigation lists, scatter plots, tree maps, geospatial maps, timelines, calendars, and more. Enterprise wiki champions have redirected their community members from email to make contributions about work in progress or the results of meetings with customers in the community wiki. Over time, these contributions can be aggregated on community member pages, projects pages, or any other related pages where a visualization would be useful. This is possible because structured wikis enable [[Content Networks|content networks]] to be formed and used. &lt;/div&gt;&lt;div class="large-4 columns"&gt;[[Image:GWFAuthoring.png|400px]]&lt;br&gt;Enterprise Wiki Collaboration&lt;/div&gt;&lt;/div&gt; 
----
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>6f02dac07c3304ae6aef7c4d94f0ae991a11539b</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Content Networks</title>
  <ns>0</ns>
  <id>215</id>
  <revision>
    <id>488</id>
    <timestamp>2015-02-26T19:02:17Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3161" xml:space="preserve">{{Breadcrumb}}
&lt;div class="row" &gt;&lt;div class="large-5 columns"&gt;Enterprise content is a network of relationships between projects, events, organizations, customers, reviews, events and topics of interest to its staff, partners, and customers. There are many information technologies that can be used to reveal these relationships. This diagram captures the increasing data controls and opportunities to collaborate with more contributors. A {{Elink|http://en.wikipedia.org/wiki/Table_(information)|table}} organizes data into rows and columns. Rows represent an item and columns represent attributes or properties of the item. The intersection of a row and a column is a cell. Cells contain data values. Data controls are limited to sorting actions. A {{Elink|http://en.wikipedia.org/wiki/Spreadsheet|spreadsheet}} is a software application used to analyze data. It consists of a set of tables with enhanced controls such as functions which can modify data values using rules pivot tables which summarize and visualize data. &lt;/div&gt;&lt;div class="large-7 columns"&gt;[[Image:TableCellsToRelationships.png|700px]] &lt;br&gt; Table Cells to Structured Wikis&lt;/div&gt;&lt;/div&gt;
&lt;div class="row" &gt;&lt;div class="large-12 columns"&gt;{{Elink|http://en.wikipedia.org/wiki/Database|Databases}} use metadata in a schema to structure and organize information as queriable tables. {{Elink|http://en.wikipedia.org/wiki/Document_management_system|Document management systems}} organize documents into hierarchies where text can be searched. A wiki represents information as a collection of linked pages. Pages can be grouped by categories and edit history is logged. A structured wiki enables authors to annotate page text with user-defined properties. These properties define relationships which can be combined and queried to produce many different views of the same information.&lt;/div&gt;&lt;/div&gt;
&lt;div class="row" &gt;&lt;div class="large-5 columns"&gt;Wikis transform a single page into a network of content. For example, a wiki could contain pages about presentations created at MITRE. A form could be used to enter the information about a presentation such as the soon-to-be famous movie, "Wikis Save MITRE." The movie could be reviewed where the reviewer could rate the movie using stars and include a comment. The movie could also be discussed or commented upon where viewers engage in a dialogue about the movie. The quality of the content about the movie could also be reviewed. Finally, readers could make lists of movies and include this movie.  One wiki page about the movie item can become a network of related pages that quality or further describe the movie. In addition, the annotations in the "Wikis Save MITRE" page such as the date, time, length, description, and tags could queried and the results embedded into additional pages about the movie. To make use of iconography to improve comprehension, to visualize content as a network or hierarchy, or to rate content, see [[Gestalt Wiki Framework Extensions]].&lt;/div&gt;&lt;div class="large-7 columns"&gt;[[Image:NetworkofPages.png|700px]]&lt;br&gt;Content Network&lt;/div&gt;&lt;div&gt;
----
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>da50b9cad5ce09385ac2942d120ac9c749bdac6b</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Breadcrumb</title>
  <ns>10</ns>
  <id>264</id>
  <revision>
    <id>592</id>
    <timestamp>2015-02-26T19:07:48Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="264" xml:space="preserve">&lt;includeonly&gt;&lt;div class="row"&gt;&lt;div class="large-12 columns" class="hierarchyText"&gt;{{#hierarchyBreadcrumb:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data|Name}}&lt;/div&gt;&lt;/div&gt;
&lt;div class="row"&gt;&lt;div class="large-12 columns"&gt;{{New Paragraph}}&lt;/div&gt;&lt;/div&gt;&lt;/includeonly&gt;</text>
    <sha1>e6bbeffbad3499881227a476c9a39a2b118ee7be</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Title Icons in Page</title>
  <ns>0</ns>
  <id>217</id>
  <revision>
    <id>492</id>
    <timestamp>2015-02-26T19:23:15Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Bclemente moved page [[Title Icons Set in Page]] to [[Title Icons in Page]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="171" xml:space="preserve">{{Breadcrumb}}
{{#set:Title Icon=UnderConstruction.png}}
{{#set:Title Icon=Article.png}}
{{#set:Title Icon=Inproceedings.png}}
{{#set:Name={{PAGENAME}}}}
[[Category:Page]]</text>
    <sha1>3832b0804d1c7db067791b0abda46d84058398d5</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Title Icons in Page and Category</title>
  <ns>0</ns>
  <id>218</id>
  <revision>
    <id>494</id>
    <timestamp>2015-02-26T19:23:44Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Bclemente moved page [[Title Icons Set in Page and Category]] to [[Title Icons in Page and Category]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="204" xml:space="preserve">{{Breadcrumb}}
{{#set:Title Icon=UnderConstruction.png}}
{{#set:Title Icon=Article.png}}
{{#set:Title Icon=Inproceedings.png}}
[[Category:Title Icon Category]]
{{#set:Name={{PAGENAME}}}}
[[Category:Page]]</text>
    <sha1>2422850acbebabbd542fe5da52d07b9411c48d6d</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Gestalt Wiki Framework Extensions</title>
  <ns>0</ns>
  <id>216</id>
  <revision>
    <id>490</id>
    <timestamp>2015-02-26T20:02:05Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1104" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
&lt;div class="row" &gt;&lt;div class="large-6 columns"&gt;
==== Description ====
The Gestalt Wiki Framework team has written over 40 extensions for MediaWiki and Semantic MediaWiki.  Eleven extensions have been contributed to the MediaWiki open source community as shown at the bottom of this page which was transcluded page from [http://www.mediawiki.org/wiki/Category:Extensions_by_MITRE MediaWiki.org]. As our extensions mature, we plan to contribute as many general purpose extensions to the MediaWiki community as funding priorities allow.  This section of the wiki provides usage documentation as well as live examples of selected GWF extensions.  As shown in the legend, the grey boxes display the wiki text, the blue boxes contain live examples, and the white boxes are links to live examples. Visit our documentation pages: {{#hierarchyChildren:Gestalt Wiki Framework Extensions|Table of Contents|Hierarchy Data|Name|template=X}}&lt;/div&gt;&lt;div class="large-6 columns"&gt;{{Legend}}&lt;/div&gt;&lt;/div&gt;
----
[[Category:Page]]
{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon={{PAGENAME}}.png}}</text>
    <sha1>04ea82d1f66b2c852f9482fe8f4b9b06913a8c05</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Legend</title>
  <ns>10</ns>
  <id>267</id>
  <revision>
    <id>600</id>
    <timestamp>2015-02-26T20:04:40Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1187" xml:space="preserve">&lt;includeonly&gt;
&lt;div style="border: solid 1px #c0c0c0;"&gt;
&lt;div class="row" style="padding:5px;"&gt;&lt;div class="small-12 columns" style="color:#009933;"&gt;'''Legend'''&lt;/div&gt;&lt;/div&gt;&lt;div  style="padding:5px;font-size:90%;"&gt;&lt;div class="row" style="margin-bottom:-3px;"&gt;&lt;div class="small-3 columns"&gt;Wiki text&lt;/div&gt;&lt;div class="small-9 columns"&gt;
{| style="background: #F0F0F0;"
|&lt;pre&gt;
{{{field|Rating|input type=rating}}}
&lt;/pre&gt;
|}&lt;/div&gt;&lt;/div&gt;
&lt;div class="row"  style="margin-bottom:-3px;"&gt;&lt;div class="small-3 columns"&gt;Live example&lt;/div&gt;&lt;div class="small-9 columns"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchyBreadcrumb:Querying|Table of Contents|Hierarchy Data|Name}}
|}&lt;/div&gt;&lt;/div&gt;
&lt;div class="row"  style="margin-bottom:-3px;"&gt;&lt;div class="small-3 columns" &gt;Live example&lt;/div&gt;&lt;div class="small-9 columns"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#rating:3|10}}
|}&lt;/div&gt;&lt;/div&gt;
&lt;div class="row"  style="margin-bottom:-3px;"&gt;&lt;div class="small-3 columns" &gt;Link to live example&lt;/div&gt;&lt;div class="small-9 columns"&gt;
{| style="border: solid 1px #D0D0D0;"
| See  [[Special:FormEdit/Review/Review:1/Bclemente | Review]] 
|}&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;
&lt;/includeonly&gt;</text>
    <sha1>9c763bc2345b735539f9f07274d6803a88d8585b</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Semantic Rating</title>
  <ns>0</ns>
  <id>222</id>
  <revision>
    <id>502</id>
    <timestamp>2015-02-26T20:17:01Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5530" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
====Description====
&lt;div class="row"&gt;&lt;div class="large-6 columns"&gt;The Semantic Rating extension adds a [http://www.mediawiki.org/wiki/Extension:Semantic_Forms Semantic Form] input type to enable users to enter a rating by clicking on stars. It also adds three parser functions to display a star rating by displaying empty (gray), full (yellow), and half stars:

* &lt;code&gt;#rating&lt;/code&gt; displays a rating inline
* &lt;code&gt;#ratingBeforeTitle&lt;/code&gt; displays a rating to the left of the title at the top of the page. 
* &lt;code&gt;#ratingAfterTitle&lt;/code&gt; displays a rating to the right of the title at the top of the page. 
__TOC__&lt;/div&gt;&lt;div class="large-6 columns"&gt;{{Legend}}&lt;/div&gt;&lt;/div&gt;
====Usage: Define a Semantic Form Rating Field====
The following will add an input field with the default maximum number of stars:
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
&lt;pre&gt;
{{{field|Rating|input type=rating}}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;"
| See working example  [[Special:FormEdit/Review/Review:1/Bclemente |An example Review Form]], See form here: [[Form:Review]]
|}
&lt;/div&gt;&lt;/div&gt;
The maximum number of stars can be set explicitly with the '''max''' parameter:
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
&lt;pre&gt;
{{{field|Rating|input type=rating|max=10}}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;"
|See working example in action ????See form here: ????
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Display a Number as a Five Star Rating====
The following displays a number as a five star rating.
&lt;div class="row" width=100% &gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:75%;"&gt;
&lt;pre&gt;
{{#rating:0}}&lt;br&gt;
{{#rating:0.5}}&lt;br&gt;
{{#rating:1}}&lt;br&gt;
{{#rating:1.5}}&lt;br&gt;
{{#rating:2}}&lt;br&gt;
{{#rating:2.5}}&lt;br&gt;
{{#rating:3}}&lt;br&gt;
{{#rating:3.5}}&lt;br&gt;
{{#rating:4}}&lt;br&gt;
{{#rating:4.5}}&lt;br&gt;
{{#rating:5}}&lt;br&gt;
{{#rating:}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;

{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#rating:0}}&lt;br&gt;
{{#rating:0.5}}&lt;br&gt;
{{#rating:1}}&lt;br&gt;
{{#rating:1.5}}&lt;br&gt;
{{#rating:2}}&lt;br&gt;
{{#rating:2.5}}&lt;br&gt;
{{#rating:3}}&lt;br&gt;
{{#rating:3.5}}&lt;br&gt;
{{#rating:4}}&lt;br&gt;
{{#rating:4.5}}&lt;br&gt;
{{#rating:5}}&lt;br&gt;
{{#rating:}}
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Display a Rating with Maximum Number of Stars====
To explicitly set the maximum number of stars to 10, use the following:
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#rating:3|10}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;

{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#rating:3|10}}
|}
&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Display an Average Rating====
The following query displays the rating using the Semantic Result Format ''average''.
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;

{{#rating:{{#ask:[[Category:Reviews]][[Item::Item:1]]|?Rating|format=average}}}} 

&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;

{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#rating:{{#ask:[[Category:Reviews]][[Item::Item:1]]|?Rating|format=average}}}}
|}
&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Display Review Results as an Average Rating====
This query displays the average rating for each item.
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
&lt;pre&gt;
{{#ask:[[Category:Items]]
|?Responsive Citation
|headers=hide
|mainlabel=-
|format=table
|class=border
|limit=5
|sort=Sorting Title
|order=ascending
| searchlabel=
}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:90%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;font-size:90%"
|{{#ask:[[Category:Items]]
|?Responsive Citation
|headers=hide
|mainlabel=-
|format=table
|class=border
|limit=5
|sort=Sorting Title
|order=ascending
| searchlabel=
}}
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Rating Before Title====
To explicitly set the number of stars to be displayed ''before'' the page title, use
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
&lt;pre&gt;
{{#ratingBeforeTitle:5}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;

{| style="border: solid 1px #D0D0D0;"
| See working example on this page: [[Rating Before Title]]
|}
&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Rating After Title====
To explicitly set the number of stars to be displayed ''after'' the page title, use
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
&lt;pre&gt;
{{#ratingAfterTitle:3}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;

{| style="border: solid 1px #D0D0D0;"
| See working example on this page: [[Rating After Title]]
|}
&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:Semantic Rating}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>8d130498264bbc007c7cb981c773f442722b1d22</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>VIKI Network Graph</title>
  <ns>0</ns>
  <id>223</id>
  <revision>
    <id>504</id>
    <timestamp>2015-02-26T20:17:44Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4772" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
====Description====
&lt;div class="row" style="background:white;" width=100%&gt;&lt;div class="large-5 columns" &gt;
'''VIKI''' (Visualization and Knowledge Integration) is an extension that displays the structure of wiki content as the inbound, outbound, and second order links for a list of wiki pages. It was implemented using D3 as a directed force layout graph visualization. In a VIKI graph, graph nodes represent individual wiki pages or web pages, while links between nodes indicate page links (i.e. one page has a hyperlink to another page, e.g. of the form &lt;nowiki&gt;[[Page Link]]&lt;/nowiki&gt;). These links are directional, where the direction of the link indicates which page links to which. If two pages link to each other, the link is bidirectional. Two pages are linked on a VIKI graph if there is a link between their nodes on the graph, i.e. either of the two pages links to the other, or they link to each other. Some wiki pages also have hyperlinks to external web pages; these pages are also displayed on the VIKI graph (with a generic wi-fi icon), but interaction with these pages is limited.
{{New Paragraph}}
The graph is pannable and zoomable using either the mouse scroll action or the zoom bar located at the bottom of the graph. Individual nodes may be dragged around and rearranged as well; the D3 graph automatically revises node positions to a local equilibrium state whenever nodes are dragged.
&lt;/div&gt;&lt;div class="large-7 columns" style="border: solid 1px #E8E8E8;background:#ADDFFF;"&gt;
{{New Paragraph}}
{{#viki:pageTitles=Gestalt Wiki Framework Extensions|width=490|height=490}}
&lt;/div&gt;&lt;/div&gt;
The graph is first initialized with a (user-defined) list of wiki pages, along with all pages linked to these pages. Pages linked to this secondary level of pages are not initially displayed – only the first order links are initially present. The user may then choose to elaborate a node; elaboration involves retrieving and displaying all linked pages for the given node’s page. Elaboration of a node expands the VIKI graph, and users may expand the graph to explore the structure of the wiki. Elaborated nodes are also called hub nodes, and the length of links to hub nodes is longer for improved graph visibility. Users may also choose to hide individual nodes and/or hide entire hubs to focus down the graph to areas of interest.
====Usage====
Users may right click on a given node to bring up a context menu of options. Below is a list of all possible options, but not all nodes may have all options as appropriate.
* ''Freeze'': this node becomes frozen in position while other nodes may move around it
* ''Visit Page'': opens the page represented by the node in a new tab or window
* ''Elaborate'': elaborates a node, as discussed previously
* ''Show Categories'': Pops up a JavaScript alert listing the categories this page belongs to. (Under construction.)
* ''Hide Node'': Removes this node and links to it from the VIKI graph.
* ''Hide Hub'': Removes this hub node and all nodes immediately linked to it from the VIKI graph, unless the linked node is itself a hub.
* ''Show All'': Adds all previously-hidden nodes and links back into the VIKI graph.

To embed a VIKI graph into a page,  the following parser function syntax is used:

&lt;div class="row" width=100%&gt;&lt;div class="large-12 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
 &lt;pre&gt;{{ #viki:pageTitles=First Page Title, Second Page Title,…|width=width|height=height|delimiter=delimiter }}&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

'''Parameters'''
* ''pageTitles'': a list of wiki pages (given by title) to comprise the initial graph (default: the current page)
* ''width'': the desired width (in pixels) of the graph (default: 1200)
* ''height'': the desired height of the graph (default: 600)
* ''delimiter'': the desired delimiter that separates between pageTitles (default: ,)

====VIKI Plugin System====
VIKI is designed to be extensible, with a built-in hook system. Developers can write MediaWiki extensions which serve as plugins to the core VIKI architecture to enhance or modify the VIKI graph behavior. Details about the plugin structure can be found at [[VIKI Plugin Structure|this page]]. Two VIKI plugins enhance functionality and/or provide compatibility support for other MediaWiki and Semantic MediaWiki extensions: 
* [[VIKI Semantic Title]] extension provides support for pages using the [http://www.mediawiki.org/wiki/Extension:SemanticTitle Semantic Title] extension
* [[VIKI Title Icon]] extension provides enhanced functionality for pages using the [[Title Icon]] extension

{{Download|http://www.mediawiki.org/wiki/Extension:VIKI}}
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>75fb38089784560678141bc7b8f13551e4371702</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>VIKI Semantic Title</title>
  <ns>0</ns>
  <id>224</id>
  <revision>
    <id>506</id>
    <timestamp>2015-02-26T20:18:52Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1187" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
&lt;div class="row"&gt;&lt;div class="large-12 columns"&gt;
====Description====
VIKI Semantic Title is an extension to the VIKI extension to handle pages which use semantic page naming. In semantic page naming, the name of a page is not a human-readable title, but rather something of a systematic format (e.g. "Item:1"), and the title of the page is set via a semantic property. Because VikiJS shows page titles for nodes, this extension ensures that the proper page display title is used rather than the systematic title.

See also the [http://www.mediawiki.org/wiki/Extension:SemanticTitle SemanticTitle] extension for more details on semantic page naming.

The citation pages used to demonstrate Semantic Rating were constructed using Semantic Titles. Instead of displaying node names using actual page names such as Item:1, Item:2, etc., the semantic property [[Property:Full Title]] as the semantic page title.
{| style="background:#ADDFFF;"
|{{#viki:pageTitles=Semantic Rating|width=900|height=600}}
|}&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:VikiSemanticTitle}}

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon=VIKI.png}}
[[Category:Page]]</text>
    <sha1>350a8ef4dd8b108abaf53656e562a3a68a8b7321</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>VIKI Title Icon</title>
  <ns>0</ns>
  <id>225</id>
  <revision>
    <id>508</id>
    <timestamp>2015-02-26T20:19:37Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="588" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
&lt;div class="row"&gt;&lt;div class="large-12 columns"&gt;
====Description====
VIKI Title Icon is an extension to the VIKI extension which adds support for [[Title Icon]]. If a page has a title icon, the title icon will render as the node logo for that page in place of its wiki logo. The VIKI graph below uses the Title Icon property for its the nodes.
{| style="background:#ADDFFF;"
|{{#viki:pageTitles=Title Icon|width=900|height=600}}
|}&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:VikiTitleIcon}}
{{#set:Title Icon=VIKI.png}}
[[Category:Page]]</text>
    <sha1>5079e1f795833e0286d585a273c84489a998ca24</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Hierarchy Builder</title>
  <ns>0</ns>
  <id>226</id>
  <revision>
    <id>510</id>
    <timestamp>2015-02-26T20:22:00Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1219" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
====Description====
&lt;div class="row" &gt;&lt;div class="large-7 columns"&gt;The Hierarchy Builder extension allows authors to create hierarchies as bullets in a page, use checkboxes to select hierarchical elements from a form, create and edit hierarchies using drag and drop, query and display the hierarchy results. The Table of Contents for this wiki is used as the hierarchy for many of the examples of the use the extension below. This page provides working examples of how to create and display hierarchies, use checkboxes to select hierarchical elements from a form, create and edit hierarchies using drag and drop. The next page provides working examples of how to [[Hierarchy Querying |query hierarchies]]. For download and installation instructions, see [http://www.mediawiki.org/wiki/Extension:HierarchyBuilder HierarchyBuilder].&lt;/div&gt;
&lt;div class="large-5 columns" style="font-size:80%;"&gt;
{{#hierarchySubtree:Gestalt Wiki Framework Extensions|Table of Contents|Hierarchy Data|displaynameproperty=Name|showroot}}
&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:HierarchyBuilder}}
__NOTOC__
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>035eb613b3bbaa82b13c1b63f3fbcf2c2d23c8de</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Selecting</title>
  <ns>0</ns>
  <id>229</id>
  <revision>
    <id>516</id>
    <timestamp>2015-02-26T20:30:09Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1700" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
==== Description ====
&lt;div class="row"&gt;&lt;div class="large-6 columns"&gt;
The hierarchySelect Semantic Form input type allows users to select a subset of pages from a hierarchy within a form to populate a multi-valued property of type Page. &lt;/div&gt; &lt;div class="large-6 columns"&gt;[[Image:ExtensionUsage.png|400px]]&lt;br&gt;Screenshot of Form:Survey&lt;/div&gt; &lt;/div&gt; 
==== Usage ====
The hierarchySelect input type can be seen in action by clicking on the "Click this Link" link. The name of the property that stores the hierarchy [[Property:Hierarchy Data]] and the page on which that property is set, [[Gestalt Extensions]], must be provided in the form in order to be able to locate the hierarchy. 

&lt;div class="row" &gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;&lt;includeonly&gt;
{{{info|page name=Survey Response_&lt;unique number;start=001&gt;|create title=Survey|edit title=Survey}}}
{{{for template|Survey}}}
{| class="formtable"
! Which extensions have you used?
| {{{field|Extensions|input type=hierarchySelect|pagename=Gestalt Extensions|propertyname=Hierarchy Data|list}}}
|}
{{{end template}}}
{{{standard input|save}}}  {{{standard input|cancel}}}
&lt;/includeonly&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;div class="large-6 columns" style="font-size:90%;"&gt;
{| style="border: solid 1px #D0D0D0;"
|{{#formlink:form=Survey|link text=Click this link|link type=link}}
|-
|Click on these pages and then open them using "Edit" dropdown action{{#ask: [[Category:Responses]]
|?Extensions
|format=table
}}
|}&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:HierarchyBuilder}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>6567a171190e2f06369774a108e0cde162575803</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Creating</title>
  <ns>0</ns>
  <id>227</id>
  <revision>
    <id>512</id>
    <timestamp>2015-02-26T20:33:36Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3660" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
====Description====
&lt;div class="row"&gt;&lt;div class="large-6 columns"&gt;
This page describes how to create hierarchies using the &lt;nowiki&gt;&lt;hierarchy&gt;&lt;/nowiki&gt; tag. There are three optional attributes the &lt;nowiki&gt;&lt;hierarchy&gt;&lt;/nowiki&gt; tag takes: ''collapsed, displaynameproperty'', and ''autonumbered''. The grey boxes on the left show the wikitext code. The blue boxes on the right show the extension in action.__TOC__&lt;/div&gt;&lt;div class="large-6 columns"&gt;{{Legend}}&lt;/div&gt;&lt;/div&gt;
====Usage: Hierarchy Expanded====
This is an example of the use of the &lt;nowiki&gt;&lt;hierarchy&gt;&lt;/nowiki&gt; tag without any attributes.
&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
&lt;hierarchy&gt;
*[[Gestalt Wiki Framework]]
**[[Hierarchy Builder]]
**[[Semantic Rating]]
**[[Title Icon]]
**[[Network Graph]]
&lt;/hierarchy&gt;
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|&lt;hierarchy&gt;
*[[Gestalt Wiki Framework]]
**[[Hierarchy Builder]]
**[[Semantic Rating]]
**[[Title Icon]]
**[[Network Graph]]
&lt;/hierarchy&gt;
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Hierarchy Collapsed====
To show a hierarchy collapsed, add the attribute ''collapsed.''
&lt;div class="row"&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:80%;"&gt;
&lt;pre&gt;
&lt;hierarchy collapsed&gt;
*[[Gestalt Wiki Framework]]
**[[Hierarchy Builder]]
**[[Semantic Rating]]
**[[Title Icon]]
**[[Network Graph]]
&lt;/hierarchy&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:90%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|&lt;hierarchy collapsed&gt;
*[[Gestalt Wiki Framework]]
**[[Hierarchy Builder]]
**[[Semantic Rating]]
**[[Title Icon]]
**[[Network Graph]]
&lt;/hierarchy&gt;
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Hierarchy With Different Display Names====
&lt;p&gt;To display a different page name, set the attribute ''displaynameproperty'' to a different property name. The citations in this wiki use the following page naming: Item:1..n. Each page in Category:Items has a property Short_Title.&lt;/p&gt;
&lt;div class="row"&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:80%;"&gt;
&lt;pre&gt;
&lt;hierarchy displaynameproperty=Short_Title&gt;
*[[Enterprise Wiki Articles]]
**[[Item:1]]
**[[Item:4]]
**[[Item:2]]
**[[Item:3]]
**[[Item:5]]
&lt;/hierarchy&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:90%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|&lt;hierarchy displaynameproperty=Short_Title&gt;
*[[Enterprise Wiki Articles]]
**[[Item:1]]
**[[Item:4]]
**[[Item:2]]
**[[Item:3]]
**[[Item:5]]
&lt;/hierarchy&gt;
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Hierarchy With Different Display Names and Element Numbers====
&lt;p&gt;Building on the example above, add the attribute ''numbered.''&lt;/p&gt;
&lt;div class="row"&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:80%;"&gt;
&lt;pre&gt;
&lt;hierarchy numbered displaynameproperty=Short_Title &gt;
*[[Enterprise Wiki Articles]]
**[[Item:1]]
**[[Item:4]]
**[[Item:2]]
**[[Item:3]]
**[[Item:5]]
&lt;/hierarchy&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:90%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|&lt;hierarchy numbered displaynameproperty=Short_Title &gt;
*[[Enterprise Wiki Articles]]
**[[Item:1]]
**[[Item:4]]
**[[Item:2]]
**[[Item:3]]
**[[Item:5]]
&lt;/hierarchy&gt;
|}&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:HierarchyBuilder}}

{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>a7fbc000af556b1199050a7ec277b170fba894f7</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Querying</title>
  <ns>0</ns>
  <id>230</id>
  <revision>
    <id>518</id>
    <timestamp>2015-02-26T21:51:29Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13244" xml:space="preserve">{{Breadcrumb}} __NOEDITSECTION__
====Description====
&lt;div class="row"&gt;&lt;div class="large-6 columns"&gt; This page describes how to use Hierarchy Builder's parser functions to query the elements in a hierarchy. __TOC__&lt;/div&gt;
&lt;div class="large-6 columns"&gt;{{Legend}}&lt;/div&gt;&lt;/div&gt;

====Usage: Hierarchy Breadcrumb====
The ''hierarchyBreadcrumb'' parser function can be used to display a hierarchy breadcrumb bar at the top of a page including the previous row, hierarchical parent row, and next row within the hierarchy.

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| current page
| Text
| ''
| The current page within the hierarchy for which the breadcrumb should be returned.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be used.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|-
| displaynameproperty
| Text
| ''
| The property containing a page's display name if using semantic page names.
|}

The parser function invocation below displays the breadcrumb for the page ''{{FULLPAGENAME}}'' within the hierarchy stored in property ''Hierarchy Data'' on the page ''Table of Contents'' using the semantic page names stored within the property ''Name'' on each page. The bar might contain the row that immediately precedes ''{{FULLPAGENAME}}'', immediately succeeds ''{{FULLPAGENAME}}'', and the hierarchical parent of ''{{FULLPAGENAME}}'' within the hierarchy on the page ''Table of Contents''.

&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#hierarchyBreadcrumb:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data|Name}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchyBreadcrumb:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data|Name}}
|}&lt;/div&gt;&lt;/div&gt;

====Usage: Hierarchy Children====
The ''hierarchyChildren'' parser function can be used to retrieve the immediate hierarchical children of a given page from a hierarchy on a specified page. 

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| page name
| Text
| ''
| The target page within the hierarchy for which the immediate children should be returned. If left empty then all root level rows will be returned instead.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be searched.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|-
| template
| Text
| ''
| The name of a template with which to display the printouts.
|-
| introtemplate
| Text
| ''
| The name of a template to display before the results if there are any.
|-
| outrotemplate
| Text
| ''
| The name of a template to display after the results if there are any.
|-
| link
| 'none' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify whether or not to display results as links if there are any results.
|-
| sep
| Text
| ','
| Used to specify the separator for returned values.
|}

The parser function takes the following three mandatory arguments in order: page name, hierarchy page, and hierarchy property. There are also the following optional arguments: ''sep'', ''template'', ''introtemplate'', ''outrotemplate'', and ''link''. The ''sep'' argument is used to specify the separator for returned values. The argument ''template'' is the name of a template with which to display the printouts. The ''introtemplate'' argument is the name of a template to display before the results if there are any. The ''outrotemplate'' argument is the name of a template to display after the results if there are any. The argument ''link'' is used to specify whether or not to display results as links if there are any results. The value of the ''link'' argument can either be empty or ''none''. By default, ''link'' is enabled.

The parser function invocation below displays the template ''Y'' followed by the immediate children of the page ''Table of Contents'' in the hierarchy stored in the property ''hierarchy property'' on the page ''hierarchy page'' after applying the template ''X'' to each result, followed by the template ''Z''.

&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#hierarchyChildren:Hierarchy Builder|Table of Contents|Hierarchy Data|template=X|introtemplate=Y|outrotemplate=Z|link=none}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchyChildren:Hierarchy Builder|Table of Contents|Hierarchy Data|template=X|introtemplate=Y|outrotemplate=Z|link=none}}
|}&lt;/div&gt;&lt;/div&gt;
====Usage: Hierarchy Parent====
The ''hierarchyParent'' parser function is used to retrieve the hierarchical parent of a given page from a hierarchy on a specified page. 

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| page name
| Text
| Mandatory
| The target page within the hierarchy for which the immediate hierarchical parent should be returned.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be searched.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|-
| template
| Text
| ''
| The name of a template with which to display the printouts.
|-
| introtemplate
| Text
| ''
| The name of a template to display before the results if there are any.
|-
| outrotemplate
| Text
| ''
| The name of a template to display after the results if there are any.
|-
| link
| 'none' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify whether or not to display results as links if there are any results.
|-
| sep
| Text
| ','
| Used to specify the separator for returned values.
|}

The parser function take the following three mandatory arguments in order: page name, hierarchy page, and hierarchy property. Additionally, there are also the following optional arguments: ''template'', ''introtemplate'', ''outrotemplate'', and ''link''. Each of these arguments behaves the same as they do for the ''hierarchyChildren ''parser function above. The argument ''template'' is the name of a template with which to display the printouts. The ''introtemplate'' argument is the name of a template to display before the results if there are any. The ''outrotemplate'' argument is the name of a template to display after the results if there are any. The argument ''link'' is used to specify whether or not to display results as links if there are any results. The value of the ''link'' argument can either be empty or ''none''. By default, ''link'' is enabled.

The parser function invocation below displays the hierarchical parent row of ''{{FULLPAGENAME}}'' within the hierarchy stored in property ''hierarchy property'' on the page ''hierarchy page name'' rendered as a hyperlink.
&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#hierarchyParent:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data|link=none}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchyParent:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data|link=none}}
|}&lt;/div&gt;&lt;/div&gt;
====Usage: Hierarchy Section Number====
The ''hierarchySectionNumber'' parser function is used to automatically compute a given page's section number within a particular hierarchy on a specified page. 

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| page name
| Text
| Mandatory
| The target page within the hierarchy for which the section number should be returned.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be searched.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|}

The parser function takes three mandatory arguments in order: page name, hierarchy page, and hierarchy property. The parser function invocation below give the section number of the page ''{{FULLPAGENAME}}'' within the hierarchy in property ''Hierarchy Data'' on the page ''[[Table of Contents]]''.

&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#hierarchySectionNumber:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchySectionNumber:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data}}
|}&lt;/div&gt;&lt;/div&gt;

====Usage: Hierarchy Subtree====
The ''hierarchySubtree'' parser function is used to render the subtree rooted at a given node within a specified hierarchy. 

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| root node
| Text
| Mandatory
| The node that forms the root of the desired subtree.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be searched.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|-
| format
| 'ul' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify the display formatting of the returned subtree. Either bulleted or hierarchical.
|-
| displaynameproperty
| Text
| ''
| The name of the property containing a page's display name. Used to support semantic page names.
|-
| showroot
| 'showroot' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify that the subtree's root should also be displayed.
|-
| collapsed
| 'collapsed' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify that the subtree should be initialized in collapsed mode.
|}

The parser function takes three mandatory arguments in order: root node, hierarchy page, and hierarchy property. If format is given as 'ul' then the subtree will be rendered as a bulleted list. Otherwise, the subtree is rendered by default as a hierarchy. If 'showroot' is given then the root of the subree will be rendered as a part of the result. By default the root of the subtree is hidden in the display. If 'collapsed' is given then the subtree will be initialized in collapsed mode. By default the subtree is not rendered in collapsed mode.

The parser function invocation below renders the subtree rooted at "Hierarchy Builder" within the hierarchy in property ''Hierarchy Data'' on the page ''Table of Contents'' as a bulleted list.

&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#hierarchySubtree:Hierarchy Builder|Table of Contents|Hierarchy Data}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchySubtree:Hierarchy Builder|Table of Contents|Hierarchy Data}}
|}&lt;/div&gt;&lt;/div&gt;
====Usage: Hierarchy Selected====
The ''hierarchySelected'' parser function is used to find and render the minimum spanning tree that contains specified rows within a hierarchy in addition to the root node of the specified hierarchy. The rendered minimum spanning tree will show each selected node with a checked box.

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| selected pages
| Text
| Mandatory
| A comma delimited list of rows that are selected within a hierarchy.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be searched.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|-
| display mode
| 'collapsed' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify whether the rendered minimum spanning tree should be initialized in collapsed mode or not.
|}

The parser function takes three mandatory arguments in order: selected pages, hierarchy page, and hierarchy property. If the display mode is given as 'collapsed' then the minimum spanning tree will be initialized in collapsed display mode. The parser function invocation below renders the minimum spanning tree in collapsed mode of the hierarchy in property ''hierarchy property'' on the page ''hierarchy page name'' which contained the hierarchy root and each of the listed page names so that the listed page names would be marked as "checked".

&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:60%;"&gt;
&lt;pre&gt;
{{#hierarchySelected:Creating,Editing,Selecting,Querying|Table of Contents|Hierarchy Data|collapsed}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchySelected:Creating,Editing,Selecting,Querying|Table of Contents|Hierarchy Data|collapsed}}
|}&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:HierarchyBuilder}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>2632ea1e3c5b8b961b5864997ef710118c562252</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>About</title>
  <ns>0</ns>
  <id>231</id>
  <revision>
    <id>520</id>
    <timestamp>2015-02-26T22:00:50Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1641" xml:space="preserve">{{Breadcrumb}}
&lt;div class="row" &gt;&lt;div class="large-6 columns"&gt;GWF wikis are hosted on virtual machines built on a LAMP stack. LAMP includes:
*{{Elink|http://en.wikipedia.org/wiki/Linux|Linux}} operating system,  
*{{Elink|http://en.wikipedia.org/wiki/Apache_HTTP_Server|Apache HTTP Server}},  
*{{Elink|http://en.wikipedia.org/wiki/MySQL|MySQL}} relational database management system, and
*{{Elink|http://en.wikipedia.org/wiki/PHP|PHP}} programming language. 
{{New Paragraph}}
Wiki software from {{Elink|http://www.mediawiki.org/wiki/MediaWiki|MediaWiki}} and {{Elink|https://semantic-mediawiki.org|Semantic MediaWiki}} is used. MediaWiki is used to run {{Elink|https://en.wikipedia.org/|Wikipedia}} and is used by {{Elink|https://wikiapiary.com/wiki/Main_Page|over 25,000}} sites.  Semantic MediaWiki is used by {{Elink|https://wikiapiary.com/wiki/Main_Page|over 1,300 sites}} to annotate page content with properties that can be queried and visualized. Many GWF extensions, some of which are MediaWiki extensions and others which are Semantic MediaWiki extensions have been contributed to the {{Elink|http://www.mediawiki.org/wiki/Category:Extensions_by_MITRE|open source community}}. All the software components used to build this GWF wiki are automatically listed on the [[Special:Version|version page]]. &lt;/div&gt;
&lt;div class="large-6 columns"&gt;[[Image:MGF.png|600px]]&lt;br&gt;GWF Stack&lt;/div&gt;&lt;/div&gt;
To learn more about Gestalt Wiki Framework, see our [[Publications|publications]], [[Team|team]], [[MITRE|enterprise]], and [[Contact |contact information]] pages.

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>cdf4b93b326c5b1d417512739184e705d57cd892</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Background</title>
  <ns>0</ns>
  <id>213</id>
  <revision>
    <id>484</id>
    <timestamp>2015-02-27T23:19:33Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3948" xml:space="preserve">{{Breadcrumb}}
&lt;div class="row" &gt;&lt;div class="large-12 columns"&gt;The broad enterprise encyclopedia, MITREpedia, was established in 2004 as a grassroots effort to capture technical enterprise knowledge as linked articles rather than bulleted presentations. The linear nature of slide presentations, however, forces authors to reduce complex subjects to a set of bullet items that are too weak to support decision-making or show the complexity of an issue. Information designer and visualization expert Edward Tufte has argued that bulleted presentations encourages simplistic thinking where ideas are squashed into lists and stories are transformed into a collection of disparate points&lt;ref&gt;See Wikipedia' article about [http://en.wikipedia.org/wiki/Edward_Tufte#Criticism_of_PowerPoint Edward Tufte views on bullet-based presentations]&lt;/ref&gt;. 
{{New Paragraph}}
MITREpedia project governance was led by a MITREpedia Users Group consisting of staff content providers and MITREpedia system administrators. As a grassroots volunteer encyclopedia, MITREpedia's structure evolved over time with the development of categories as a by-product of authoring articles. Navigational elements to improve findability included a featured article, recent contributions, categories, and enterprise "fast jumps"-- named enterprise links. Topic-specific "wiki portals," a major findability element for Wikipedia, were not adopted.
{{New Paragraph}}
The Gestalt Wiki Framework (GWF) effort began as a single Semantic MediaWiki-based wiki about human language technology (HLT) in 2006. The purpose was to produce a dynamic, growing knowledge repository for MITRE's work in HLT to maintain continuous enterprise situational awareness, i.e. "the big picture or "Gestalt" about HLT at MITRE without creating periodic surveys, scheduling meetings, conducting enterprise searches, and analyzing financial project data. Languapedia's sidebar was customized for the HLT community to link to projects, people, events, and HLT topics. &lt;/div&gt;&lt;/div&gt;
&lt;div class="row" &gt;&lt;div class="large-4 columns"&gt;Librarian staff discovered Languapedia after searching for an approach to develop a highly structured, highly findable biosecurity collection.  Biopedia was the second wiki to be constructed. Robopedia, the third wiki, grew at a significantly more rapid pace than Languapedia nor Biopedia. Languapedia was established as an experiment without socialization within the community. Biopedia was developed as part of a diffuse group's needs to establish biosecurity as an important up and coming interest. Robopedia represented the needs of a dedicated group of technologists who depend heavily on technical documentation. It currently contains ~8,800 pages, has ~150 users, and won a MITRE Knowledge Management Award in 2012. Robopedia became the poster wiki for many GWF wikis developed at MITRE as well as GWF wikis developed for MITRE customers. &lt;/div&gt;&lt;div class="large-8 columns"&gt;[[Image:Reuse.png|800px]]&lt;br&gt;Gestalt Wiki Influence Path&lt;/div&gt;&lt;/div&gt;
&lt;div class="row" &gt;&lt;div class="large-12 columns"&gt;As the team grew from one to seven, we developed best practices for GWF extension development as well as wiki and wiki farm development to help us work across multiple funding sources and customers simultaneously. In 2014, MITREpedia was transitioned to the McLean, VA Gestalt Wiki Framework team. It was upgraded from MediaWiki 1.13 to 1.23 from XML page exports because the MySQL database was so old that the update script failed to run. With MITREpedia's 25,000 pages, we have 60,000 pages on active wikis and 57,000 pages in read-only archive. Our vision is to work towards federating all the Gestalt Wiki Framework wikis with MITREpedia as the entry point for enterprise wiki knowledge and the topic-specific wikis.  Learn more about today's [[Gestalt Wiki Framework]]. &lt;/div&gt;&lt;/div&gt;
----
{{RefList}}
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>0c789e2fdfef1ab499622b1036a62a690a53f052</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Gestalt Wiki Framework</title>
  <ns>0</ns>
  <id>212</id>
  <revision>
    <id>482</id>
    <timestamp>2015-02-27T23:22:30Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3872" xml:space="preserve">{{Breadcrumb}}
&lt;div class="row" &gt;&lt;div class="large-8 columns"&gt;The '''[[Contact|Gestalt Wiki Framework]]''' (GWF) is a set of patterns and open source software that enables groups to build enterprise knowledge using structured wikis. This is our showcase for both ''enterprise knowledge stewards'' who are interested in wiki-based knowledge management and ''wiki builders'' who want to learn how to use GWF extensions. 
{{New Paragraph}}
Enterprise knowledge stewards may want to read more about the [[Background |background]] of the evolution and use of GWF in the enterprise as well as [[Enterprise Collaboration |enterprise collaboration with wikis]] and how enterprise content becomes a [[Content Networks|content network]].  Wiki-based enterprise knowledge management using GWF involves authors contributing content using forms.  These contributions may be combined with enterprise data,  queried, and visualized. Visualizations include automatically computed tables, tag clouds, bar charts, pie charts, time lines, calendars, and network graphs to enable readers to see the "big picture" of enterprise community knowledge. GWF allows authors to contribute content once and use that content in many ways.  The name "Gestalt" was chosen to reflect the evolving "big picture" of enterprise knowledge as communities collaboratively create, combine, and use their collective contributions towards a greater purpose.
{{New Paragraph}}
Wiki builders may be interested in jumping ahead to the [[Gestalt Wiki Framework Extensions|extensions documentation section]]. As a showcase for GWF extensions, we used many extension features throughout the site. For example, the green asterisk logo next to the title of this page is an example of the [[Title Icon]] extension.The information contained in the Table of Contents on the right is used in the green breadcrumb bar at the top of this page to help users navigate pages sequentially. Both the Table of Contents and the breadcrumbs are features provided by the [[Hierarchy Builder]] extension.
{{New Paragraph}}
Our team has built over 70 unique wikis since 2006. Half of these wikis are currently actively used at MITRE and on customer networks. Enterprise wiki collaboration is different than Wikipedian collaboration. Many enterprises lack 100,000+ volunteer editors with an evolved wiki culture. We have found that in addition to adapting wiki technology to the enterprise,  wiki success occurs when a community champion successfully articulates the purpose of a wiki and transforms existing business processes away from the dependency on document-based email collaboration. Read more about [[Enterprise Collaboration|enterprise collaboration]] and how wikis can help.
&lt;!--
As shown in the interactive [[Table of Contents]] on the right, this site is organized into three sections. The first section describes the [[Background |background]] of the GWF, as well as two concepts: how [[Enterprise Collaboration |enterprise collaboration]] can be conducted using a wiki and how the structure of the content becomes a [[Content Networks |network]]. The second section documents selected [[Gestalt Wiki Framework Extensions |extensions]] and provides working examples. The third section includes additional information about our [[Publications|publications]], [[Team|team]], [[MITRE|enterprise]], and [[Contact |contact information]].--&gt;
&lt;/div&gt;&lt;div class="large-4 columns" style="font-size:70%;background: white !important;"&gt;[[Image:GWFAuthoringMosaic.png|400px]]&lt;br&gt;Gestalt: The whole is greater than the sum of its parts.&lt;br&gt;{{#hierarchySubtree:Table of Contents|Table of Contents|Hierarchy Data|displaynameproperty=Name|showroot}}
&lt;/div&gt;&lt;/div&gt; 
----
There are [[Special:Statistics|{{NUMBEROFPAGES}}]] pages in this wiki. 
[[To do]]
{{DISPLAYTITLE:Gestalt Wiki Framework}}
{{#set:Name={{PAGENAME}}}}__NOTOC__
[[Category:Page]]</text>
    <sha1>09e70b09e205cbb4e8b74ca9972dbc3f8e81c297</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Collapse top</title>
  <ns>10</ns>
  <id>110</id>
  <revision>
    <id>261</id>
    <timestamp>2015-04-06T00:02:07Z</timestamp>
    <contributor>
      <username>Shirayuki</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1457" xml:space="preserve">&lt;noinclude&gt;
{{languages}}
&lt;/noinclude&gt;&lt;div style="display:{{{display|block}}};margin-{{dir|{{pagelang}}|right|left}}:{{{indent|0px}}};{{{extrastyle|}}}"&gt;&lt;!-- NOTE: width renders incorrectly if added to main STYLE section--&gt;
{| &lt;!-- Template:Collapse top --&gt; class="navbox mw-collapsible {{{{{|safesubst:}}}#if:{{{expand|}}}||mw-collapsed}}" style="background: {{{bg1|transparent}}}; text-align: {{dir|{{pagelang}}|right|left}}; border: {{{border|1px}}} solid {{{b-color|silver}}}; margin-top: 0.2em; {{{{{|safesubst:}}}#if:{{{width|}}}|width:{{{width}}};}}"
|-
! style="background-color: {{{bg|#F8FCFF}}}; text-align:{{{{{|safesubst:}}}#if:{{{left|}}}|{{dir|{{pagelang}}|right|left}}|center}}; font-size:112%; color: {{{fc|black}}};" | {{{1|{{{title|{{{reason|{{{header|{{{heading|Extended content}}} }}} }}} }}} }}}   
{{{{{|safesubst:}}}#if:{{{warning|{{{2|}}}}}}
|{{{{{|safesubst:}}}!}}-
{{{{{|safesubst:}}}!}} style="text-align:center; font-style:italic;" {{{{{|safesubst:}}}!}} {{{2|The following is a closed debate. {{strongbad|Please do not modify it.}} }}} }}
|-
| style="border: solid {{{border2|1px silver}}}; padding: {{{padding|8px}}}; background-color: {{{bg2|white}}}; font-size:112%;" {{{{{|safesubst:}}}!}}&lt;noinclude&gt;
&lt;center&gt;''The following content has been placed in a collapsed box for improved usability.''&lt;/center&gt;
{{ {{TNTN|Collapse bottom}} }}
{{ {{TNTN|Documentation}} }}
[[Category:Formatting templates{{translation}}]]
&lt;/noinclude&gt;</text>
    <sha1>58b88ddc94c40339f599638719179f4058670e35</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Navbox</title>
  <ns>10</ns>
  <id>121</id>
  <revision>
    <id>285</id>
    <timestamp>2015-04-06T11:06:09Z</timestamp>
    <contributor>
      <username>Edokter</username>
      <id>0</id>
    </contributor>
    <comment>Again, make any necessary fixes in the MODULE. If you don't know how, raise the issue on the talk page.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="94" xml:space="preserve">&lt;includeonly&gt;{{#invoke:Navbox|navbox}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>fe9b964401f895918ee4fe078678f1722a3c41ec</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Nmbox</title>
  <ns>10</ns>
  <id>137</id>
  <revision>
    <id>323</id>
    <timestamp>2015-04-19T07:33:33Z</timestamp>
    <contributor>
      <username>Shirayuki</username>
      <id>0</id>
    </contributor>
    <comment>dir</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="599" xml:space="preserve">&lt;table class="nmbox" style="border:1px solid #AAA; border-collapse:collapse; clear:both; font-size:85%; margin: 0.5em 0"&gt;
&lt;tr style="background:#EEF3E2"&gt;
{{#if:{{{image|}}}{{{header|}}}
| &lt;th class="mbox-image" style="white-space:nowrap; padding:4px 1em; border-{{dir|{{pagelang}}|left|right}}:1px solid #aaa"&gt;{{{image|}}} {{{header|}}}&lt;/th&gt;
| &lt;td class="mbox-empty-cell"&gt;&lt;/td&gt;   &lt;!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --&gt;
}}
&lt;td class="mbox-text" style="background:#F6F9ED"&gt;{{{text|}}}&lt;/td&gt;
&lt;/tr&gt;&lt;/table&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>3e5942f8af86a878f6abd3a6eeec367502baea89</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Nested Tabs 2</title>
  <ns>0</ns>
  <id>239</id>
  <revision>
    <id>536</id>
    <timestamp>2015-05-05T11:57:50Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <comment>Created page with "&lt;div style="font-size:80%;"&gt; &lt;div class="section-container auto"  data-section&gt; &lt;div class="section"&gt; &lt;p class="title" style="font-size:small;" data-section-title&gt;Background&lt;/..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2262" xml:space="preserve">&lt;div style="font-size:80%;"&gt;
&lt;div class="section-container auto"  data-section&gt;
&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Background&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Introduction|{{:Gestalt Wiki Framework}}}}
{{Tab||Background|{{:Background}}}}
{{Tab||Enterprise Collaboration|{{:Enterprise Collaboration}}}}
{{Tab||Content Networks|{{:Content Networks}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Wiki Design&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Wiki Development&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Configure a Wiki|[[Image:UnderConstruction.png|50px]]}} 
{{Tab||Create Classes|[[Image:UnderConstruction.png|50px]]}}  
{{Tab||Create Queries and Visualizations|[[Image:UnderConstruction.png|50px]]}}  
{{Tab||Patterns|[[Image:UnderConstruction.png|50px]]}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Gestalt Wiki Framework Extensions&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Introduction|{{:Gestalt Wiki Framework Extensions}}}}
{{Tab||Title Icon|{{:Title Icon}}}} 
{{Tab||Semantic Rating|{{:Semantic Rating}}}}  
{{Tab||VIKI Network Graph|{{:VIKI Network Graph}}}}  
{{Tab||VIKI Semantic Title|{{:VIKI Semantic Title}}}}
{{Tab||VIKI Title Icon|{{:VIKI Title Icon}}}}
{{Tab||Hierarchy Builder|{{:Hierarchy Builder}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;About&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Publications|{{:Publications}}}}
{{Tab||Team|{{:Team}}}}
{{Tab||MITRE|{{:MITRE}}}}
{{Tab||Contact|{{:Contact}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;
&lt;/div&gt;
__NOTOC__
 {{#set:Hide Title Icon=all}}</text>
    <sha1>c8a0aaf4f28e87f141edba6963927368fddb3de0</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Presentation</title>
  <ns>10</ns>
  <id>260</id>
  <revision>
    <id>582</id>
    <timestamp>2015-05-19T11:43:15Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="749" xml:space="preserve">&lt;includeonly&gt;{| class="wikitable"
! Description
| {{{Description|}}}
|-
! Authors
|  {{#arraymap:{{{Authors|}}}|,|@@@@|[[User:@@@@]]}} 
|-
! Date
| {{{Has date|}}}
|}
{{#if:{{{File|}}}|
{{#widget:Iframe
|url={{filepath:{{{File}}}}}
|width=900
|height=800
|border=0
}}}}
&lt;div style="display:none;"&gt;
{{#set:Name={{{Name|}}}}}
{{#set:Description={{{Description|}}}}}
{{#arraymap:{{{Authors|}}}|,|@@@@|{{#set:Authors=@@@@}}}} 
{{#set:Has date={{{Has date|}}}}}
{{#set:Responsive Presentation=&lt;div class="row"&gt;&lt;div class="large-2 columns"&gt;[[Image:{{{Thumbnail}}}|200px|link={{PAGENAME}}]]&lt;/div&gt;&lt;div class="large-10 columns"&gt;[[{{PAGENAME}}]]&lt;/div&gt;&lt;/div&gt;}}
[[Category:Presentations]]
&lt;/div&gt;
&lt;/includeonly&gt;&lt;noinclude&gt;[[Category:Framework Pages]]&lt;/noinclude&gt;</text>
    <sha1>2a607dea97787ff2a039fecffd8ded441ff5e27c</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Form:Presentation</title>
  <ns>106</ns>
  <id>261</id>
  <revision>
    <id>584</id>
    <timestamp>2015-05-19T11:45:13Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="411" xml:space="preserve">&lt;includeonly&gt;
{{{for template|Presentation}}}
{| class="formtable"
! Description
| {{{field|Description}}}
|-
! Authors:
| {{{field|Authors}}}
|-
! Date
| {{{field|Has date}}}
|-
! Thumbnail
| {{{field|Thumbnail|uploadable}}}
|-
! File
| {{{field|File|uploadable}}}
|}
{{{end template}}}

{{{standard input|save}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;
&lt;noinclude&gt;
[[Category:Framework Pages]]
&lt;/noinclude&gt;</text>
    <sha1>aec2aff2b37674cc42c9dc0386c81e1dbab4506c</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Property:Has date</title>
  <ns>102</ns>
  <id>163</id>
  <revision>
    <id>586</id>
    <parentid>373</parentid>
    <timestamp>2015-05-19T11:55:37Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <comment>Created page with "[[Has type::Date]] [[Category:Framework Pages]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47" xml:space="preserve">[[Has type::Date]] [[Category:Framework Pages]]</text>
    <sha1>0029eb2c66667853bff2027f47be98e28562e980</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Blogs and Presentations</title>
  <ns>0</ns>
  <id>232</id>
  <revision>
    <id>522</id>
    <timestamp>2015-05-19T12:00:23Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="540" xml:space="preserve">__NOEDITSECTION__
====Blogs====
[[Image:BlogOrigins.png|200px|link=https://publish.mitre.org/kde/2015/03/26/gestalt-wikis-at-mitre-march-2015]] [https://publish.mitre.org/kde/2015/03/26/gestalt-wikis-at-mitre-march-2015/ Gestalt Wikis at MITRE Knowledge Driven Enterprise Blog]
----
====Presentations====
{{#ask: [[Category:Presentations]] |limit=100
|?Responsive Presentation=
|?Has date=Date
|sort=Has date
|order=descending
|mainlabel=-
|format=table
}}

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon=Presentations.png}}
[[Category:Page]]</text>
    <sha1>72a0948a6ecfd70509d7ac36ad1520340cc17141</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Team</title>
  <ns>0</ns>
  <id>233</id>
  <revision>
    <id>524</id>
    <timestamp>2015-05-19T12:02:32Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="189" xml:space="preserve">{{#ask: [[Category:Users]][[Linkedin-url::+]]
|?Linkedin-url=
|?Name=
|format=template
|template=Gallery
}}
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>9b40ff5b461351505cc3046dee205ad0f0f54985</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>MITRE</title>
  <ns>0</ns>
  <id>235</id>
  <revision>
    <id>528</id>
    <timestamp>2015-05-19T12:02:42Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="841" xml:space="preserve">&lt;div class="row" &gt;&lt;div class="large-8 columns"&gt;Our team works at MITRE, a not-for-profit organization that operates research and development centers sponsored by the federal government. MITRE operates FFRDCs—federally funded research and development centers—which are unique organizations that assist the United States government with:

* Scientific research and analysis
* Development and acquisition
* Systems engineering and integration

MITRE also has an independent research program that explores new and expanded uses of technologies to solve customers' problems. For more information about MITRE, visit [http://www.mitre.org mitre.org].&lt;/div&gt;&lt;div class="large-4 columns"&gt;[[Image:MITRE1.png|500px|MITRE McLean, VA]]&lt;br&gt;MITRE, McLean, VA&lt;/div&gt;&lt;/div&gt;

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>102774df2e2047838096c6b4ab061e543b226a6e</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Contact</title>
  <ns>0</ns>
  <id>236</id>
  <revision>
    <id>530</id>
    <timestamp>2015-05-19T12:02:52Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="330" xml:space="preserve">If you are interested in 

*Learning more about the Gestalt Wiki Framework,
*How enterprise wikis can help government agencies build and share knowledge, or
*Providing us feedback on this site,

Please send email to: [mailto:bclemente@mitre.org Gestalt Wiki Framework team].

{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>73e6ba07c11f1e0839bd9e2a41939258ff0912e9</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Keywords</title>
  <ns>0</ns>
  <id>262</id>
  <revision>
    <id>588</id>
    <timestamp>2015-05-19T14:21:28Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <comment>Created page with "&lt;div style="display:none;"&gt; {{#vardefine:keyword|{{lc:{{#urldecode:{{#urlget:keyword}}}}}}}}  &lt;/div&gt; {{#ask:[[Category:Research Proposals]][[Keywords::{{#var:keyword}}]] |?Ave..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="483" xml:space="preserve">&lt;div style="display:none;"&gt;
{{#vardefine:keyword|{{lc:{{#urldecode:{{#urlget:keyword}}}}}}}} 
&lt;/div&gt;
{{#ask:[[Category:Research Proposals]][[Keywords::{{#var:keyword}}]]
|?Average Rating Stars
|?Citation
|mainlabel=-
|headers=hide
|class=citationtable
|limit=50
|searchlabel=
|sort=Average Rating Number
|order=desc
}}

&lt;div style="display:none;"&gt;
{{#set:Dynamic Display=$keyword}}
{{#set:Logo Link=Keywords.png}}
{{DISPLAYTITLE:{{#var:keyword}}}}
[[Category:Framework Pages]]
&lt;/div&gt;</text>
    <sha1>ad18314a82d7b8c5bc77819db0cd653f023cd104</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Property:Keyword</title>
  <ns>102</ns>
  <id>263</id>
  <revision>
    <id>590</id>
    <timestamp>2015-05-19T14:33:56Z</timestamp>
    <contributor>
      <username>Bclemente</username>
      <id>0</id>
    </contributor>
    <comment>Created page with "This is a property of type [[Has type::Text]]. [[Category:Framework Pages]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:GetFallback</title>
  <ns>10</ns>
  <id>132</id>
  <revision>
    <id>313</id>
    <timestamp>2015-05-19T21:46:02Z</timestamp>
    <contributor>
      <username>Matiia</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/99.119.254.205|99.119.254.205]] ([[User talk:99.119.254.205|talk]]) to last revision by [[User:Shirayuki|Shirayuki]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="906" xml:space="preserve">{{#switch: {{Uselang|lang={{{1|}}}}}
| af | fy | li | nl-informal | vls | zea = nl
| arz = ar
| be-tarask = be-x-old
| be-x-old = be-tarask &lt;!-- same language; be-x-old is used on be-x-old.wikipedia but be-tarask is the preferred code --&gt;
| crh-cyrl | crh-latn = crh
| ckb | mzn | glk = fa
| als | bar | de-formal | de-at | de-ch | frr | ksh = de
| hif-deva | hif-latn = hif
| ike-cans | ike-latn = ike
| kk-arab | kk-cyrl | kk-latn | kk-cn | kk-kz | kk-tr = kk
| ku-latn | ku-arab = ku
| mg | br | co | frp | ht | ty | wa = fr
| nds = nds-nl
| nds-nl | pdt = nds
| pt-br = pt
| ruq-cyrl | ruq-grek | ruq-latn = ruq
| sr-ec | sr-el = sr
| tg-cyrl | tg-latn = tg
| tt-cyrl | tt-latn = tt
| vec = it
| zh | zh-cn | zh-my | zh-sg = zh-hans
| zh-hk | zh-mo | zh-tw = zh-hant
| szl | csb = pl
| en-gb = en 
| #default = {{#if: {{{default|}}} | {{{default|}}} | en }}
}}&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>b81791cc126e09f5e9e4c149056a58ba8b929a9d</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Collapse top/doc</title>
  <ns>10</ns>
  <id>141</id>
  <revision>
    <id>331</id>
    <timestamp>2015-05-26T21:21:29Z</timestamp>
    <contributor>
      <username>SPage (WMF)</username>
      <id>0</id>
    </contributor>
    <comment>mention [[w:Template:Collapse top]] for documentation</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="376" xml:space="preserve">&lt;noinclude&gt;{{Documentation subpage}}
{{timw|{{BASEPAGENAME}}}}
&lt;/noinclude&gt;
&lt;!-- PUT HERE THE DOCUMENTATION --&gt;
Use with {{tl|Collapse bottom}}, putting the content to be collapsed between the two templates.

This template has many parameters ''that should be documented here''.
For now, see the documentation for [[w:Template:Collapse top|the equivalent template on enwiki]].</text>
    <sha1>f6192f75f65394f03685259cce62518779d67256</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Tlx</title>
  <ns>10</ns>
  <id>91</id>
  <revision>
    <id>311</id>
    <parentid>229</parentid>
    <timestamp>2015-07-03T03:07:39Z</timestamp>
    <contributor>
      <username>Be..anyone</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>-colon</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="398" xml:space="preserve">{{[[{{#if:{{{SISTER|}}}|{{{SISTER}}}Template|{{ns:Template}}}}:{{{1|Tlx}}}|{{{1|Tlx}}}]]&lt;!--
--&gt;{{#if:{{{2|}}}|&amp;#124;{{{2}}}}}&lt;!--
--&gt;{{#if:{{{3|}}}|&amp;#124;{{{3}}}}}&lt;!--
--&gt;{{#if:{{{4|}}}|&amp;#124;{{{4}}}}}&lt;!--
--&gt;{{#if:{{{5|}}}|&amp;#124;{{{5}}}}}&lt;!--
--&gt;{{#if:{{{6|}}}|&amp;#124;{{{6}}}}}&lt;!--
--&gt;{{#if:{{{7|}}}|&amp;#124;{{{7}}}}}&lt;!--
--&gt;{{#if:{{{8|}}}|&amp;#124;''...''}}}}&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>31fa8846f3adf381b3a4943183ffd00c2489a2ff</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Phpi</title>
  <ns>10</ns>
  <id>103</id>
  <revision>
    <id>247</id>
    <timestamp>2015-07-08T17:29:43Z</timestamp>
    <contributor>
      <username>Krinkle</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="277" xml:space="preserve">{{inline-code|{{{1}}}|lang=php}}&lt;noinclude&gt;
&lt;templatedata&gt;
{
	"params": {
		"1": {
			"label": "Content",
			"description": "The PHP program code to be displayed.",
			"type": "string",
			"required": true
		}
	}
}
&lt;/templatedata&gt;
[[Category:Formatting templates]]
&lt;/noinclude&gt;</text>
    <sha1>10be38885e779a372c5765a3b22ba9aaad06850e</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Para</title>
  <ns>10</ns>
  <id>112</id>
  <revision>
    <id>267</id>
    <timestamp>2015-08-25T09:13:25Z</timestamp>
    <contributor>
      <username>Hashar</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>7 revisions imported from [[:w:en:Template:Para]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="267" xml:space="preserve">&lt;code class="nowrap" {{#if:{{{plain|}}}|style="border:none;background-color:inherit;color:inherit;"}}&gt;&amp;#124;{{#if:{{{1|}}}|{{{1}}}&amp;#61;}}{{{2|}}}&lt;/code&gt;&lt;noinclude&gt;
{{Documentation}}
&lt;!--Categories and interwikis go near the bottom of the /doc subpage.--&gt;
&lt;/noinclude&gt;</text>
    <sha1>66770157bb51b0aabb5b874e4f1bb8f04c80915c</sha1>
  </revision>
</page>
<page arvcontinue="20150210182706|303">
  <title>Template:Tl</title>
  <ns>10</ns>
  <id>24</id>
  <revision>
    <id>309</id>
    <parentid>24</parentid>
    <timestamp>2015-08-25T09:13:34Z</timestamp>
    <contributor>
      <username>Hashar</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>4 revisions imported from [[:w:en:Template:Tl]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25" xml:space="preserve">#REDIRECT[[Template:Tlx]]</text>
    <sha1>5d2f5bb7c52bc1bc7c1afe735011378ee521ec3c</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Documentation</title>
  <ns>10</ns>
  <id>84</id>
  <revision>
    <id>263</id>
    <parentid>222</parentid>
    <timestamp>2015-09-07T15:29:45Z</timestamp>
    <contributor>
      <username>Paladox</username>
      <id>0</id>
    </contributor>
    <comment>Undo revision 1872326 by [[Special:Contributions/Krinkle|Krinkle]] ([[User talk:Krinkle|talk]]) Fixed problem now reverted part of the protection code in module:documentation.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="182" xml:space="preserve">{{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}&lt;noinclude&gt;
&lt;!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --&gt;
&lt;/noinclude&gt;</text>
    <sha1>ce7fd93f18c46b4fa871bf679afd05cbda72d8c4</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Translation</title>
  <ns>10</ns>
  <id>139</id>
  <revision>
    <id>327</id>
    <timestamp>2015-09-22T11:06:56Z</timestamp>
    <contributor>
      <username>Jdforrester (WMF)</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/LisaNurmalaSari|LisaNurmalaSari]] ([[User talk:LisaNurmalaSari|talk]]) to last revision by [[User:This, that and the other|This, that and the other]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="489" xml:space="preserve">{{#ifeq:
  {{lc:{{#titleparts:{{FULLPAGENAME}}|1|-1}}}}&lt;!-- broken test; we should restrict to accept only subpages that could match a lowercase language code; keep any uppercase letter meaning not a language code --&gt;
| {{lc:{{#language:{{#titleparts:{{FULLPAGENAME}}|1|-1}}}}}}&lt;!-- broken test; fails on some languages whose  autonym is identical to their lowercase code --&gt;
|
| /{{#titleparts:{{FULLPAGENAME}}|1|-1}}
}}&lt;noinclude&gt;
{{documentation}}

[[Category:Translation]]
&lt;/noinclude&gt;</text>
    <sha1>df4871b4aa9beb7ee2f6e276d9819d0a4dfc4541</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:ApiParam</title>
  <ns>10</ns>
  <id>127</id>
  <revision>
    <id>299</id>
    <timestamp>2015-09-23T10:10:55Z</timestamp>
    <contributor>
      <username>Shirayuki</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="748" xml:space="preserve">&lt;includeonly&gt;*{{{bullet|}}} &lt;code {{#if:{{{required|}}}|style="font-weight:bold"}}&gt;{{{1|{{{name|}}}}}}&lt;/code&gt;{{#if:{{{2|{{{description|}}}}}}|&amp;#58; {{{2|{{{description|}}}}}}}}{{#if:{{{maxallowed|}}}|&amp;#32;No more than {{{maxallowed}}} ({{{maxallowedbot|{{#switch:{{{maxallowed}}}|50=500|500=5000}}}}} for bots) allowed.}}{{#if:{{{type|}}}|&amp;#32;'''Type''': {{{type}}}}}{{#if:{{{values|}}}|&amp;#32;Possible values: {{{values}}}.}}{{#if:{{{default|}}}|&amp;#32;(Default: {{{default}}})}}{{#if:{{{version|}}}|&amp;#32;{{MW version-inline|{{{version}}}+}}}}{{#if:{{{deprecated|}}}|&amp;#32;{{Deprecated-inline|{{{deprecated}}}}}}}{{#if:{{{removed|}}}|&amp;#32;{{ {{TNTN|Removed-inline}} |{{{removed}}}}}}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{ {{TNTN|Documentation}} }}
&lt;/noinclude&gt;</text>
    <sha1>c3ec38a9643cc68da7d82786a2db6192c709f250</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Jsi</title>
  <ns>10</ns>
  <id>104</id>
  <revision>
    <id>249</id>
    <timestamp>2015-09-25T06:16:04Z</timestamp>
    <contributor>
      <username>SPage (WMF)</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>document</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="158" xml:space="preserve">{{inline-code|{{{1}}}|lang=javascript}}&lt;noinclude&gt;

Invokes {{tl|inline-code}} with &lt;code&gt;lang=javascript&lt;/code&gt;
[[Category:Formatting templates]]&lt;/noinclude&gt;</text>
    <sha1>5830e6fb23f49e101e38b7861f4daa0304a55e40</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Inline-code</title>
  <ns>10</ns>
  <id>105</id>
  <revision>
    <id>251</id>
    <timestamp>2015-09-25T06:18:13Z</timestamp>
    <contributor>
      <username>SPage (WMF)</username>
      <id>0</id>
    </contributor>
    <comment>document</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="340" xml:space="preserve">{{#tag:syntaxhighlight|{{{1|input}}}|lang={{{lang|php}}}|enclose=none}}&lt;noinclude&gt;

== Usage ==
: Some text, then &lt;nowiki&gt;{{Inline-code | 1=wfDebug( $text, $dest = 'all' );}}&lt;/nowiki&gt; and more text.

produces
:Some text, then {{Inline-code | 1=wfDebug( $text, $dest = 'all' );}} and more text.

[[Category:Formatting templates]]&lt;/noinclude&gt;</text>
    <sha1>b60139d46d6d072f26f3ea63670145f9b31a9fe6</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Pagelang</title>
  <ns>10</ns>
  <id>138</id>
  <revision>
    <id>325</id>
    <timestamp>2015-11-29T10:51:26Z</timestamp>
    <contributor>
      <username>Wiki13</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/76.164.234.13|76.164.234.13]] ([[User talk:76.164.234.13|talk]]) to last revision by [[User:Stemoc|Stemoc]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="613" xml:space="preserve">{{#ifeq:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}|{{#titleparts:{{{1|{{PAGENAME}}}}}|1}}||{{#ifeq:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}|{{lc:{{PAGENAME:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}}}}}|{{#ifeq:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}|{{urlencode:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}}}|{{#ifeq:{{lc:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}}}|{{ucfirst:{{lc:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}}}}}||{{#switch:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}|doc|layout|sandbox|testcases|init|preload=|#default={{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}}}}}}}}}}}&lt;noinclude&gt;{{Documentation}}&lt;/noinclude&gt;</text>
    <sha1>58a30c2368e3eec4f48178a05f99574a886ee439</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Dir</title>
  <ns>10</ns>
  <id>130</id>
  <revision>
    <id>305</id>
    <timestamp>2015-12-03T20:32:06Z</timestamp>
    <contributor>
      <username>SVG</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Protected "[[Template:Dir]]": Highly visible template: regular vandalism ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="208" xml:space="preserve">{{#switch:{{lc:{{{1|{{int:lang}}}}}}}|ar|arc|arz|azb|bcc|ckb|bqi|dv|fa|fa-af|glk|ha|he|kk-arab|kk-cn|ks|ku-arab|mzn|pnb|prd|ps|sd|ug|ur|ydd|yi={{{2|rtl}}}|{{{3|ltr}}}}}&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>7d9c312af67f9eff96e7bdfce0f77cb52ca72aea</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:-</title>
  <ns>10</ns>
  <id>131</id>
  <revision>
    <id>307</id>
    <timestamp>2015-12-05T03:38:08Z</timestamp>
    <contributor>
      <username>Matiia</username>
      <id>0</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Henky anisyafrizal sabarudin|Henky anisyafrizal sabarudin]] ([[User talk:Henky anisyafrizal sabarudin|talk]]) to last revision by [[User:Matiia|Matiia]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="76" xml:space="preserve">&lt;br style="clear: {{{1|both}}};" /&gt;&lt;noinclude&gt;
{{Documentation}}&lt;/noinclude&gt;</text>
    <sha1>ff24c103813c340e95b3035eab8f1662c8649747</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Languages</title>
  <ns>10</ns>
  <id>134</id>
  <revision>
    <id>317</id>
    <timestamp>2015-12-20T03:14:36Z</timestamp>
    <contributor>
      <username>Shirayuki</username>
      <id>0</id>
    </contributor>
    <comment>translation tweaks</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4965" xml:space="preserve">{{nmbox
 | header = '''[[Project:Language policy|{{Languages/Title|{{SUBPAGENAME}}}}]]'''
 | text = 
'''[[{{{1|:{{NAMESPACE}}:{{BASEPAGENAME}}}}}|English]]''' {{Languages/Lang|af|{{{1|}}}|
}}{{Languages/Lang|ar|{{{1|}}}|
}}{{Languages/Lang|ast|{{{1|}}}|
}}{{Languages/Lang|az|{{{1|}}}|
}}{{Languages/Lang|bcc|{{{1|}}}|
}}{{Languages/Lang|bg|{{{1|}}}|
}}{{Languages/Lang|br|{{{1|}}}|
}}{{Languages/Lang|bn|{{{1|}}}|
}}{{Languages/Lang|bs|{{{1|}}}|
}}{{Languages/Lang|ca|{{{1|}}}|
}}{{Languages/Lang|cs|{{{1|}}}|
}}{{Languages/Lang|da|{{{1|}}}|
}}{{Languages/Lang|de|{{{1|}}}|
}}{{Languages/Lang|diq|{{{1|}}}|
}}{{Languages/Lang|el|{{{1|}}}|
}}{{Languages/Lang|eo|{{{1|}}}|
}}{{Languages/Lang|es|{{{1|}}}|
}}{{Languages/Lang|fa|{{{1|}}}|
}}{{Languages/Lang|fi|{{{1|}}}|
}}{{Languages/Lang|fr|{{{1|}}}|
}}{{Languages/Lang|gl|{{{1|}}}|
}}{{Languages/Lang|gu|{{{1|}}}|
}}{{Languages/Lang|he|{{{1|}}}|
}}{{Languages/Lang|hi|{{{1|}}}|
}}{{Languages/Lang|hu|{{{1|}}}|
}}{{Languages/Lang|hy|{{{1|}}}|
}}{{Languages/Lang|id|{{{1|}}}|
}}{{Languages/Lang|io|{{{1|}}}|
}}{{Languages/Lang|it|{{{1|}}}|
}}{{Languages/Lang|ja|{{{1|}}}|
}}{{Languages/Lang|ka|{{{1|}}}|
}}{{Languages/Lang|kk|{{{1|}}}|
}}&lt;span class="autonym"&gt;{{Languages/Lang|km|{{{1|}}}|
}}&lt;/span&gt;{{Languages/Lang|ko|{{{1|}}}|
}}{{Languages/Lang|ksh|{{{1|}}}|
}}{{Languages/Lang|kw|{{{1|}}}|
}}{{Languages/Lang|la|{{{1|}}}|
}}{{Languages/Lang|min|{{{1|}}}|
}}{{Languages/Lang|mk|{{{1|}}}|
}}{{Languages/Lang|ml|{{{1|}}}|
}}&lt;span class="autonym"&gt;{{Languages/Lang|mr|{{{1|}}}|
}}&lt;/span&gt;{{Languages/Lang|ms|{{{1|}}}|
}}{{Languages/Lang|nl|{{{1|}}}|
}}{{Languages/Lang|no|{{{1|}}}|
}}{{Languages/Lang|oc|{{{1|}}}|
}}{{Languages/Lang|or|{{{1|}}}|
}}{{Languages/Lang|pl|{{{1|}}}|
}}{{Languages/Lang|pt|{{{1|}}}|
}}{{Languages/Lang|pt-br|{{{1|}}}|
}}{{Languages/Lang|ro|{{{1|}}}|
}}{{Languages/Lang|ru|{{{1|}}}|
}}{{Languages/Lang|si|{{{1|}}}|
}}{{Languages/Lang|sk|{{{1|}}}|
}}{{Languages/Lang|sl|{{{1|}}}|
}}{{Languages/Lang|so|{{{1|}}}|
}}{{Languages/Lang|sq|{{{1|}}}|
}}{{Languages/Lang|sr|{{{1|}}}|
}}{{Languages/Lang|sv|{{{1|}}}|
}}{{Languages/Lang|ta|{{{1|}}}|
}}{{Languages/Lang|th|{{{1|}}}|
}}{{Languages/Lang|tr|{{{1|}}}|
}}{{Languages/Lang|uk|{{{1|}}}|
}}{{Languages/Lang|vi|{{{1|}}}|
}}{{Languages/Lang|yi|{{{1|}}}|
}}{{Languages/Lang|yue|{{{1|}}}|
}}{{Languages/Lang|zh|{{{1|}}}|
}}{{Languages/Lang|zh-hans|{{{1|}}}|
}}{{Languages/Lang|zh-hant|{{{1|}}}|
}}{{Languages/Lang|zh-tw|{{{1|}}}}}|
}}&lt;includeonly&gt;{{#if:{{Languages/Lang|af|{{{1|}}}|
}}{{Languages/Lang|ar|{{{1|}}}|
}}{{Languages/Lang|ast|{{{1|}}}|
}}{{Languages/Lang|az|{{{1|}}}|
}}{{Languages/Lang|bcc|{{{1|}}}|
}}{{Languages/Lang|bg|{{{1|}}}|
}}{{Languages/Lang|br|{{{1|}}}|
}}{{Languages/Lang|bn|{{{1|}}}|
}}{{Languages/Lang|bs|{{{1|}}}|
}}{{Languages/Lang|ca|{{{1|}}}|
}}{{Languages/Lang|cs|{{{1|}}}|
}}{{Languages/Lang|da|{{{1|}}}|
}}{{Languages/Lang|de|{{{1|}}}|
}}{{Languages/Lang|diq|{{{1|}}}|
}}{{Languages/Lang|el|{{{1|}}}|
}}{{Languages/Lang|eo|{{{1|}}}|
}}{{Languages/Lang|es|{{{1|}}}|
}}{{Languages/Lang|fa|{{{1|}}}|
}}{{Languages/Lang|fi|{{{1|}}}|
}}{{Languages/Lang|fr|{{{1|}}}|
}}{{Languages/Lang|gl|{{{1|}}}|
}}{{Languages/Lang|gu|{{{1|}}}|
}}{{Languages/Lang|he|{{{1|}}}|
}}{{Languages/Lang|hi|{{{1|}}}|
}}{{Languages/Lang|hu|{{{1|}}}|
}}{{Languages/Lang|hy|{{{1|}}}|
}}{{Languages/Lang|id|{{{1|}}}|
}}{{Languages/Lang|io|{{{1|}}}|
}}{{Languages/Lang|it|{{{1|}}}|
}}{{Languages/Lang|ja|{{{1|}}}|
}}{{Languages/Lang|ka|{{{1|}}}|
}}{{Languages/Lang|kk|{{{1|}}}|
}}{{Languages/Lang|km|{{{1|}}}|
}}{{Languages/Lang|ko|{{{1|}}}|
}}{{Languages/Lang|ksh|{{{1|}}}|
}}{{Languages/Lang|kw|{{{1|}}}|
}}{{Languages/Lang|la|{{{1|}}}|
}}{{Languages/Lang|min|{{{1|}}}|
}}{{Languages/Lang|mk|{{{1|}}}|
}}{{Languages/Lang|ml|{{{1|}}}|
}}{{Languages/Lang|mr|{{{1|}}}|
}}{{Languages/Lang|ms|{{{1|}}}|
}}{{Languages/Lang|nl|{{{1|}}}|
}}{{Languages/Lang|no|{{{1|}}}|
}}{{Languages/Lang|oc|{{{1|}}}|
}}{{Languages/Lang|or|{{{1|}}}|
}}{{Languages/Lang|pl|{{{1|}}}|
}}{{Languages/Lang|pt|{{{1|}}}|
}}{{Languages/Lang|pt-br|{{{1|}}}|
}}{{Languages/Lang|ro|{{{1|}}}|
}}{{Languages/Lang|ru|{{{1|}}}|
}}{{Languages/Lang|si|{{{1|}}}|
}}{{Languages/Lang|sk|{{{1|}}}|
}}{{Languages/Lang|sl|{{{1|}}}|
}}{{Languages/Lang|so|{{{1|}}}|
}}{{Languages/Lang|sq|{{{1|}}}|
}}{{Languages/Lang|sr|{{{1|}}}|
}}{{Languages/Lang|sv|{{{1|}}}|
}}{{Languages/Lang|ta|{{{1|}}}|
}}{{Languages/Lang|th|{{{1|}}}|
}}{{Languages/Lang|tr|{{{1|}}}|
}}{{Languages/Lang|uk|{{{1|}}}|
}}{{Languages/Lang|vi|{{{1|}}}|
}}{{Languages/Lang|yi|{{{1|}}}|
}}{{Languages/Lang|yue|{{{1|}}}|
}}{{Languages/Lang|zh|{{{1|}}}|
}}{{Languages/Lang|zh-hans|{{{1|}}}|
}}{{Languages/Lang|zh-hant|{{{1|}}}|
}}{{Languages/Lang|zh-tw|{{{1|}}}}}
||[[Category:Languages pages without translations]]}}&lt;!--
--&gt;[[Category:Languages pages]]&lt;!--
--&gt;{{#ifeq:{{translation}}|/en||[[Category:Languages pages{{translation}}]]}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{ {{TNTN|documentation}} }}
[[Category:Exclude in print]]
&lt;/noinclude&gt;</text>
    <sha1>aa0a3f30852c3d71ab7babadb5e80e3de93f2495</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1</id>
    <timestamp>2015-12-23T05:07:16Z</timestamp>
    <contributor>
      <username>MediaWiki default</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="592" xml:space="preserve">&lt;strong&gt;MediaWiki has been successfully installed.&lt;/strong&gt;

Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]</text>
    <sha1>8e0aa2f2a7829587801db67d0424d9b447e09867</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Target</title>
  <ns>0</ns>
  <id>2</id>
  <revision>
    <id>2</id>
    <timestamp>2015-12-23T07:18:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{#display_map: 32.477635895824065,-86.42840132117271~TARGET~ ~Target-icon-24.png~ALPHA; 32.47635327711175,-86.42690598964691~TARGET~ ~Target-icon-24.png~ALPHA |rectangles=32...."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="273" xml:space="preserve">{{#display_map: 32.477635895824065,-86.42840132117271~TARGET~ ~Target-icon-24.png~ALPHA; 32.47635327711175,-86.42690598964691~TARGET~ ~Target-icon-24.png~ALPHA
|rectangles=32.47800306083119,-86.42626762390137:32.47609331733586,-86.42908930778503~link:http://j.mp/1SatLty
}}</text>
    <sha1>48a2b2aa6f5b53eb1fb8a83b29b988d3f5094374</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Category:Hidden categories</title>
  <ns>14</ns>
  <id>3</id>
  <revision>
    <id>3</id>
    <timestamp>2015-12-23T13:58:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This is the Hidden categories category."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39" xml:space="preserve">This is the Hidden categories category.</text>
    <sha1>8b2860dde47e23122f9a43d0e019c1a76b286b20</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Cell system</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>4</id>
    <timestamp>2015-12-23T17:07:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{for|the general use of a cellular structure by an organization, such as by a business|Cellular organization (disambiguation)}} {{redirect|Sleeper cell}} {{Use dmy dates|date..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39395" xml:space="preserve">{{for|the general use of a cellular structure by an organization, such as by a business|Cellular organization (disambiguation)}}
{{redirect|Sleeper cell}}
{{Use dmy dates|date=July 2011}}
{{multiple issues|
{{Essay-like|date=July 2011}}
{{POV|date=September 2012}}
{{Original research|date=January 2015}}
{{cleanup|reason=Poorly written, poorly referenced, marked essay-like (mostly user Hcberkowitz's edits; see page history) and POV issues and generally underlinked|date=January 2015}}
{{cleanup-rewrite|date=January 2015}}
{{Expert-subject|date=January 2015}}
}}

{{terrorism}}
A '''clandestine cell''' structure is a method for organizing a group of people like [[French resistance|resistance]] fighters or terrorists in such a way that it can more effectively resist penetration by an opposing organization (e.g., a law enforcement organization). In a cell structure, each small group of people in the cell only know the identities of the people in their cell; as such, if a cell member is apprehended and interrogated, he or she will not know the identities of the higher-ranking individuals in the organization. Depending on the group's [[philosophy]], its operational area, the communications technologies available, and the nature of the mission, it can range from a strict hierarchy to an extremely distributed organization. It is also a method used by [[organized crime|criminal organizations]], [[undercover]] operatives, and unconventional warfare (UW) units led by [[special forces]]. Historically, clandestine organizations have avoided electronic communications, because [[signals intelligence]] is a strength of conventional militaries and counterintelligence organizations.{{citation needed|date=August 2012}}

In the context of [[tradecraft]], [[covert operation|covert]] and [[clandestine operation|clandestine]] are not synonymous. As noted in the definition (which has been used by the United States and NATO since World War II) in a covert operation the identity of the sponsor is concealed, while in a clandestine operation the operation itself is concealed. Put differently, clandestine means "hidden", while covert means "deniable". The adversary is aware that a covert activity is happening, but does not know who is doing it, and certainly not their sponsorship. Clandestine activities, however, if successful, are completely unknown to the adversary, and their function, such as espionage, would be neutralized if there was any awareness of the activity.

A '''sleeper cell''' refers to a cell, or isolated grouping of [[sleeper agent]]s that lies dormant until it receives orders or decides to act.

==History==

=== Provisional Irish Republican Army===
As opposed to the [[French Resistance]], the modern [[Provisional Irish Republican Army]] (PIRA) has a history going back to Irish revolutionary forces in the early 20th century, but has little external control.  Its doctrine and organization have changed over time, given factors such as the independence of 26 of Ireland's 32 counties, the continued British control of Northern Ireland and the simple passage of time and changes in contemporary thinking and technology.&lt;ref name=Leahy&gt;{{cite web
 | url = http://cgsc.cdmhost.com/cgi-bin/showfile.exe?CISOROOT=/p4013coll2&amp;CISOPTR=386&amp;filename=387.pdf
 |format=PDF| author = Leahy, Kevin C.
 | year = 2005
 | title = The Impact of Technology on the Command, Control, and Organizational Structure of Insurgent Groups
 | accessdate=2007-12-04
}}&lt;/ref&gt;

Officially, the PIRA is hierarchical, but, especially as British security forces became more effective, changed to a semiautonomous model for its operational and certain of its support cells (e.g., transportation, intelligence, cover and security).&lt;ref name=GreenBook&gt;{{cite web
 | url = https://web.archive.org/web/20110606012137/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html
 | author = Irish Republican Army
 | title = The Green Book
 | accessdate=2007-12-04
|archiveurl=https://web.archive.org/web/20070616132240/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html|archivedate=2007-06-16}}&lt;/ref&gt; Its leadership sees itself as guiding and consensus-building. The lowest-level cells, typically of 2-5 people, tend to be built by people with an existing personal relationship. British counterinsurgents could fairly easily understand the command structure, but not the workings of the operational cells.

The IRA has an extensive network of inactive or sleeper cells, so new ''ad hoc'' organizations may appear for any specific operation.

===World War II French Resistance===
In World War II, [[Operation Jedburgh]] teams parachuted into occupied France to lead unconventional warfare units.&lt;ref name=Hall&gt;{{cite book
 | author = Hall, Roger
 | title = You're Stepping on my Cloak and Dagger
 | publisher = Bantam Books
 | year =1964
}}&lt;/ref&gt;&lt;ref name=SOETO&gt;{{cite book
 | chapterurl = http://www.history.army.mil/books/wwii/70-42/70-423.htm
 | chapter = Chapter 3: Special Operations in the European Theater
 | publisher = [[United States Army Center of Military History]]
| url = http://www.history.army.mil/books/wwii/70-42/70-42c.htm
| title = U.S. Army Special Operations in World War II
| first = David W.
| last = Hogan
| id = CMH Pub 70-42
|year = 1992
| location = Washington, D.C.
}}&lt;/ref&gt; They would be composed of two officers, one American or British, and the other French, the latter preferably from the area into which they landed. The third member of the team was a radio operator.

Especially through the French member, they would contact trusted individuals in the area of operation, and ask them to recruit a team of trusted subordinates (i.e., a subcell). If the team mission were sabotage, reconnaissance, or espionage, there was no need to meet in large units. If the team was to carry out direct action, often an unwise mission unless an appreciable number of the locals had military experience, it would be necessary to assemble into units for combat. Even then, the hideouts of the leadership were known only to subcell leaders. The legitimacy of the Jedburgh team came from its known affiliation with Allied powers, and it was a structure more appropriate for UW than for truly clandestine operations.

===National Front for the Liberation of South Vietnam===
Also known as the [[Viet Cong]], this organization grew from earlier anticolonial groups fighting the French, as well as anti-Japanese guerillas during World War II.&lt;ref name=VietCong&gt;{{cite book
 | author = Pike, Douglas
 | title = Viet Cong: Organization and Technique of the National Liberation Front of South Vietnam
 | publisher = MIT Press
 | year = 1970
}}&lt;/ref&gt;
Its command, control, and communication techniques derived from the experiences of these earlier insurgent groups. The group had extensive support from North Vietnam, and, indirectly, from the Soviet Union. It had parallel political and military structures, often overlapping. See [[Viet Cong and PAVN strategy and tactics]].
[[Image:Vcnvastructure4rev.jpg|thumb|right |A dual, but sometimes overlapping, Party and Military structure was top-down]]
The lowest level consisted of three-person cells who operated quite closely, and engaging in the sort of [[self-criticism]] common, as a bonding method, to Communist organizations.{{Citation needed|date=June 2014}}

==Parallel organizations==
The NLF and PIRA, as well as other movements, have chosen to have parallel political and military organizations. In the case of the NLF, other than some individuals with sanctuary in North Vietnam, the political organization could not be overt during the [[Vietnam War]]. After the war ended, surviving NLF officials held high office.

In the case of the PIRA, its political wing, [[Sinn Féin]], became increasingly overt, and then a full participant in politics. [[Hamas]] and [[Hezbollah]] also have variants of overt political/social service and covert military wings.

The overt political/social–covert military split avoided the inflexibility of a completely secret organization. Once an active insurgency began, the secrecy {{clarify span|could limit|date=January 2015}}&lt;!-- what? --&gt; freedom of action, distort information about goals and ideals, and restrict communication within the insurgency.&lt;ref name=FM3-24&gt;{{cite web
 | title = FM 3-24: Counterinsurgency
 | author = US Department of the Army
 |date=December 2006
 | url = https://fas.org/irp/doddir/army/fm3-24.pdf
|format=PDF}}&lt;/ref&gt; In a split organization, the public issues can be addressed overtly, while military actions were kept covert and intelligence functions stay clandestine.

==External support==
Many cell systems still receive, with due attention to security, support from the outside. This can range from leaders, trainers and supplies (such as the Jedburgh assistance to the French Resistance), or a safe haven for overt activities (such as the NLF spokesmen in Hanoi).

External support need not be overt. Certain Shi'a groups in Iraq, for example, do receive assistance from Iran{{Citation needed|date=March 2009}}, but this is not a public position of the government of Iran, and may even be limited to factions of that government.  Early US support to the Afghan Northern Alliance against the Taliban used clandestine operators from both the [[CIA]] and [[United States Army Special Forces]]. As the latter conflict escalated, the US participation became overt.

Note that both [[unconventional warfare]] (UW) (guerrilla operations) and [[foreign internal defense]] (FID) (counterinsurgency) may be covert and use cellular organization.

In a covert FID mission, only selected host nation (HN) leaders are aware of the foreign support organization. Under [[Operation White Star]], US personnel gave covert FID assistance to the Royal Lao Army starting in 1959, became overt in 1961, and ceased operations in 1962.

==Models of insurgency and associated cell characteristics==
While different kinds of insurgency differ in where they place clandestine or covert cells, when certain types of insurgency grow in power, the cell system is deemphasized. Cells still may be used for leadership security, but, if overt violence by organized units becomes significant, cells are less important. In Mao's three-stage doctrine,&lt;ref name=Mao1967&gt;{{cite book
 | title = On Protracted War
 | author = Mao,  Zedong | authorlink = Mao Zedong
 | year = 1967
 | publisher = Foreign Language Press, Beijing
}}&lt;/ref&gt; cells are still useful in Phase II to give cover to part-time guerillas, but, as the insurgency creates full-time military units in Phase III, the main units are the focus, not the cells. The [[Eighth Route Army]] did not run on a cell model.

When considering where cells exist with respect to the existing government, the type of insurgency needs to be considered. One US Army reference was Field Manual 100-20, which has been superseded by FM3-07.&lt;ref name=FM3-07&gt;{{cite web
 | title = FM 3-07 (formerly FM 100-20): Stability Operations and Support Operations
 | date = 20 February 2003
 | author = US Department of the Army
 | url = https://atiam.train.army.mil/soldierPortal/atia/adlsc/view/altfmt/9630-1
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; Drawing on this work, Nyberg (a [[United States Marine Corps]] officer) extended the ideas to describe four types of cell system, although his descriptions also encompass types of insurgencies that the cell system supports.&lt;ref name=Nyberg&gt;{{Cite journal
 | title = Insurgency: The Unsolved Mystery
 | first = Eric N. | last = Nyberg
 | publisher = US Marine Corps University Command and Staff College
 | year = 1991
 | url = http://www.globalsecurity.org/military/library/report/1991/NEN.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt;  At present, there is a new type associated with transnational terrorist insurgencies.

# Traditional: the slowest to form, this reflects a principally indigenous insurgency, initially with limited goals. It is more secure than others, as it tends to grow from people with social, cultural or family ties. The insurgents resent a government that has failed to recognize  tribal, racial, religious or linguistic groups "who perceive that the government has denied their rights and interests and work to establish or restore them. They seldom seek to overthrow the government or control the whole society; however, they frequently attempt to withdraw from government control through autonomy or semiautonomy." The Mujahideen in Afghanistan and the Kurdish revolt in Iraq illustrate the traditional pattern of insurgency. [[al-Qaeda]] generally operates in this mode, but if they become strong enough in a given area, they may change to the mass-oriented form.
# Subversive: Usually driven by an organization that contains at least some of the governing elite, some being sympathizers already in place, and others who penetrate the government. When they use violence, it has a specific purpose, such as coercing voters, intimidating officials, and disrupting and discrediting the government. Typically, there is a political arm (such as  [[Sinn Féin]] or the [[Viet Cong|National Liberation Front]]) that directs the military in planning carefully coordinated violence. "Employment of violence is designed to show the system to be incompetent and to provoke the government to an excessively violent response which further undermines its legitimacy." The [[Nazi]] rise to power, in the 1930s, is another example of subversion. Nazi members of parliament and street fighters were hardly clandestine, but the overall plan of the Nazi leadership to gain control of the nation was hidden. "A subversive insurgency is suited to a more permissive political environment which allows the insurgents to use both legal and illegal methods to accomplish their goals. Effective government resistance may convert this to a critical-cell model.
# Critical-cell: Critical cell is useful when the political climate becomes less permissive than one that allowed shadow cells. While other cell types try to form intelligence cells within the government, this type sets up "[[Continuity of government|shadow government]]" cells that can seize power once the system is destroyed both by external means and the internal subversion. This model fits the classic [[coup d'etat]],&lt;ref name=Luttwak&gt;{{cite book
 | title = Coup d'etat: A Practical Handbook
 | year = 1968
 | author = Luttwak, Edward | authorlink = Edward Luttwak
 | publisher = Harvard University Press
}}&lt;/ref&gt; and often tries to minimize violence. Variants include the [[Sandinista]] takeover of an existing government weakened by external popular revolution. "Insurgents also seek to infiltrate the government's institutions, but their object is to destroy the system from within." Clandestine cells form inside the government. "The use of violence remains covert until the government is so weakened that the insurgency's superior organization seizes power, supported by the armed force. One variation of this pattern is when the insurgent leadership permits the popular revolution to destroy the existing government, then emerges to direct the formation of a new government. Another variation is seen in the [[Cuba]]n revolution&lt;ref name=Guevara&gt;{{cite book
 | author = Guevara, Ernesto "Che"
 | title = On Guerilla Warfare
 | publisher = Praeger
 | year = 1961
}}&lt;/ref&gt; and is referred to as the foco (or Cuban model) insurgency. This model involves a single, armed cell which emerges in the midst of degenerating government legitimacy and becomes the nucleus around which mass popular support rallies.  The insurgents use this support to establish control and erect new institutions."
# Mass-oriented: where the subversive and covert-cell systems work from within the government, the mass-oriented builds a government completely outside the existing one, with the intention of replacing it. Such "insurgents patiently construct a base of passive and active political supporters, while simultaneously building a large armed element of guerrilla and regular forces.  They plan a protracted campaign of increasing violence to destroy the government and its institutions from the outside.  They have a well-developed ideology and carefully determine their objectives.  They are highly organized and effectively use propaganda and guerrilla action to mobilize forces for a direct political and military challenge to the government." The revolution that produced the [[Peoples' Republic of China]], the [[American Revolution]], and the [[Shining Path]] insurgency in Peru are examples of the mass-oriented model. Once established, this type of insurgency is extremely difficult to defeat because of its great depth of organization.

==Classic models for cell system operations==
Different kinds of cell organizations have been used for different purposes. This section focuses on clandestine cells, as would be used for [[espionage]], [[sabotage]], or the organization for [[unconventional warfare]]. When unconventional warfare starts using overt units, the cell system tends to be used only for sensitive leadership and intelligence roles.&lt;ref name=Mao1967 /&gt; The examples here will use [[CIA cryptonym]]s as a naming convention used to identify members of the cell system. Cryptonyms begin with a two-letter country or subject name (e.g., AL), followed with an arbitrary word. It is considered elegant to have the code merge with the other letters to form a pronounceable word.

===Operations under official cover===
Station BERRY operates, for country B, in target country BE. It has three case officers and several support officers. Espionage operation run by case officers under diplomatic cover, they would have to with the basic recruiting methods described in this article. Case officer BETTY runs the local agents BEN and BEATLE. Case officer BESSIE runs BENSON and BEAGLE.
[[Image:Wdip-Cell-0.png|thumb|Representative diplomatic-cover station and networks]]

Some recruits, due to the sensitivity of their position or their personalities not being appropriate for cell leadership, might not enter cells but be run as singletons, perhaps by other than the recruiting case officer. Asset BARD is a different sort of highly sensitive singleton, who is a joint asset of the country B, and the country identified by prefix AR. ARNOLD is a case officer from the country AR embassy, who knows only the case officer BERTRAM and the security officer BEST. ARNOLD does not know the station chief of BERRY or any of its other personnel. Other than BELL and BEST, the Station personnel only know BERTRAM as someone authorized to be in the Station, and who is known for his piano playing at embassy parties. He is covered as Cultural Attache, in a country that has very few pianos. Only the personnel involved with BARD know that ARNOLD is other than another friendly diplomat.

In contrast, BESSIE and BETTY know one another, and procedures exist for their taking over each other's assets in the event one of the two is disabled.

Some recruits, however, would be qualified to recruit their own subcell, as BEATLE has done. BESSIE knows the identity of BEATLE-1 and BEATLE-2, since he had them checked by headquarters counterintelligence before they were recruited. Note that a cryptonym does not imply anything about its  designee, such as gender.

===Clandestine presence===
The diagram of "initial team presence" shows that two teams, ALAN and ALICE, have successfully entered an area of operation, the country coded AL, but are only aware of a pool of potential recruits, and have not yet actually recruited anyone. They communicate with one another only through headquarters, so compromise of one team will not affect the other.
[[Image:Wnoc-Cell-0.png|thumb|left |Initial team presence by 2 separate clandestine teams with no official cover]]

Assume that in team ALAN, ALASTAIR is one of the officers with local contacts, might recruit two cell leaders, ALPINE and ALTITUDE. The other local officer in the team, ALBERT, recruits ALLOVER.  When ALPINE recruited two subcell members, they would be referred to as ALPINE-1 and ALPINE-2.

ALPINE and ALTITUDE only know how to reach ALASTAIR, but they are aware of at least some of other team members' identity should ALASTAIR be unavailable, and they would accept a message from ALBERT. Most often, the identity (and location) of the radio operator may not be shared. ALPINE and ALTITUDE, however, do not know one another. They do not know any of the members of team ALICE.

The legitimacy of the subcell structure came from the recruitment process, originally by the case officer and then by the cell leaders. Sometimes, the cell leader would propose subcell member names to the case officer, so the case officer could have a headquarters name check run before bringing the individual into the subcell. In principle, however, the subcell members would know ALPINE, and sometimes the other members of the ALPINE cell if they needed to work together; if ALPINE-1 and ALPINE-2 had independent assignments, they might not know each other. ALPINE-1 and ALPINE-2 certainly would not know ALASTAIR or anyone in the ALTITUDE or ALLOVER cells.
[[Image:Wnoc-Cell-1.png|thumb|Clandestine teams have built initial subcells]]

As the networks grow, a subcell leader might create his own cell, so ALPINE-2 might become the leader of the ALIMONY cell.

===Fault-tolerant cellular structures===
Modern communications theory has introduced methods to increase fault tolerance in cell organizations. In the past, if cell members only knew the cell leader, and the leader was neutralized, the cell was cut off from the rest of the organization. Game theory and graph theory have been applied to the study of optimal covert network design (see Lindelauf, R.H.A. et al. 2009. The influence of secrecy on the communication structure of covert networks. Social Networks 31: 126-137).

If a traditional cell had independent communications with the foreign support organization, headquarters might be able to arrange its reconnection. Another method is to have impersonal communications "side links" between cells, such as a pair of [[dead drop]]s, one for Team ALAN to leave "lost contact" messages to be retrieved by Team ALICE, and another dead drop for Team ALICE to leave messages for Team ALAN.

These links, to be used only on losing contact, do not guarantee a contact. When a team finds a message in its emergency drop, it might do no more than send an alert message to headquarters. Headquarters might determine, through [[SIGINT]] or other sources, that the enemy had captured the leadership and the entire team, and order the other team not to attempt contact. If headquarters can have reasonable confidence that there is a communications failure or partial compromise, it might send a new contact to the survivors.

When the cut-off team has electronic communications, such as the Internet, it has a much better chance of eluding surveillance and getting emergency instructions than by using a dead drop that can be under physical surveillance.

==Non-traditional models, exemplified by al-Qaeda==
Due to cultural differences, assuming the ''al-Qaeda Training Manual''&lt;ref name=AQTM&gt;{{cite web
 | url = https://fas.org/irp/world/para/aqmanual.pdf
 |format=PDF| title = al-Qaeda training manual
 | publisher = US Southern District Court, US New York City Attorney's Office, entered as evidence in Africa embassy bombings
}}&lt;/ref&gt; is authentic, eastern cell structures may differ from the Western mode. "Al-Qaida's minimal core group, only accounting for the leadership, can also be viewed topologically as a ring or chain network, with each leader/node heading their own particular hierarchy.

"Such networks function by having their sub-networks provide information and other forms of support (the ‘many-to-one’ model), while the core group supplies ‘truth’ and decisions/directions (the ‘one-to-many’ model). Trust and personal relationships are an essential part of the Al-Qaida network (a limiting factor, even while it provides enhanced security). Even while cell members are trained as ‘replaceable’ units, ‘vetting’ of members occurs during the invited training period under the observation of the core group.&lt;ref name=Sleepers&gt;{{cite web
 | url = http://www.metatempo.com/huntingthesleepers.pdf
 |format=PDF| title = Hunting the Sleepers: Tracking al-Qaida's Covert Operatives
 | date = 2001-12-31
 | author = Decision Support Systems, Inc.
 | accessdate = 2007-11-17
}}&lt;/ref&gt;

Cells of this structure are built outwards, from an internal leadership core. Superficially, this might be likened to a Western cell structure that emanates from a headquarters, but the Western centrality is bureaucratic, while structures in other non-western cultures builds on close personal relationships, often built over years, perhaps involving family or other in-group linkages. Such in-groups are thus extremely hard to infiltrate; infiltration has a serious chance only outside the in-group. Still, it may be possible for an in-group to be compromised through [[COMINT]] or, in rare cases, by compromising a member.

The core group is logically a ring, but is superimposed on an inner hub-and-spoke structure of ideological authority. Each member of the core forms another hub and spoke system (see [[#Infrastructure cells|infrastructure cells]]), the spokes leading to infrastructure cells under the supervision of the core group member, and possibly to operational groups which the headquarters support. Note that in this organization, there is a point at which the operational cell becomes autonomous of the core. Members surviving the operation may rejoin at various points.
[[Image:T-Cell-0.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

Osama, in this model, has the main responsibility of commanding the organization and being the spokesman on propaganda video and audio messages distributed by the propaganda cell. The other members of the core each command one or more infrastructure cells.

While the tight coupling enhances security, it can limit flexibility and the ability to scale the organization. This in-group, while sharing tight cultural and ideological values, is not committed to a bureaucratic process.

"Members of the core group are under what could be termed 'positive control'—long relationships
and similar mindsets make 'control' not so much of an issue, but there are distinct roles, and position (structural, financial, spiritual) determines authority, thus making the core group a hierarchy topologically.&lt;ref name=Sleepers /&gt;

In the first example of the core, each member knows how to reach two other members, and also knows the member(s) he considers his ideological superior. Solid lines show basic communication, dotted red arrows show the first level of ideological respect, and dotted blue arrows show a second level of ideological respect.

If Osama, the most respected, died, the core would reconstitute itself. While different members have an individual ideological guide, and these are not the same for all members, the core would reconstitute itself with Richard as most respected.

Assume there are no losses, and Osama can be reached directly only by members of the core group. Members of outer cells and support systems might know him only as "the Commander", or, as in the actual case of al-Qaeda, Osama bin Laden's face is recognizable worldwide, but only a few people know where he was or even how to contact him.

===Infrastructure cells===
Any clandestine or covert service, especially a non-national one, needs a variety of technical and administrative functions. Some of these services include:&lt;ref name=Sleepers /&gt;

# Forged documents and counterfeit currency
# Apartments and hiding places
# Communication means
# Transportation means
# Information
# Arms and ammunition
# Transport

Other functions include psychological operations, training, and finance.

A national intelligence service&lt;ref name=CIAsupport&gt;{{cite web
 | url = https://www.cia.gov/offices-of-cia/mission-support/who-we-are.html
 | author = US Central Intelligence Agency
 | title = Support to Mission: Who We Are
 | accessdate = 2007-11-19
}}&lt;/ref&gt;
has a support organization to deal with services such as finance, logistics, facilities (e.g., [[#Safehouses and Other Meeting Places|safehouses]]), information technology, communications, training, weapons and explosives, medical services, etc. Transportation alone is a huge function, including the need to buy tickets without drawing suspicion, and, where appropriate, using private vehicles. Finance includes the need to transfer money without coming under the suspicion of financial security organizations.

Some of these functions, such as finance, are far harder to operate in remote areas, such as the [[FATA]] of [[Pakistan]], than in cities with large numbers of official and unofficial financial institutions, and the communications to support them. If the financial office is distant from the remote headquarters, there is a need for [[couriers]], who must be trusted to some extent, but they may not know the contents of their messages or the actual identity of sender and/or receiver. The couriers, depending on the balance among type and size of message, security, and technology available, may memorize messages, carry audio or video recordings, or hand-carry computer media.
[[Image:T-Cell-1.png|thumb|Core group and infrastructure cells; military cells in training]]

"These cells are socially embedded (less so than the core group, however), structurally embedded, functionally embedded (they are specialized into a domain), and knowledge base-specific (there does not seem to be a great deal of cross-training, or lateral mobility in the organization). Such cells are probably subjected to a mixture of positive and negative control ("do this, do these sorts of things, don’t do that")."&lt;ref name=Sleepers /&gt;

{| class="wikitable"
&lt;caption&gt;Core Structure of Non-National Group&lt;/caption&gt;
|-
! Member
! Infrastructure commanded
|-
| Richard
| Finance
|-
| Anton
| Military training/operations 1
|-
| Hassan
| Military training/operations 2
|-
| David
| Transportation
|-
| Kim
| Communications and propaganda
|}

The leaders of military cells are responsible for training them, and, when an operation is scheduled, selecting the operational commander, giving him the basic objective and arranging whatever support is needed, and then release him from tight control to execute the meeting. Depending on the specific case, the military leaders might have direct, possibly one-way, communications with their cells, or they might have to give Kim the messages to be transmitted, by means that Anton and Hassan have no need to know.

Note that Anton does not have a direct connection to Kim. Under normal circumstances, he sacrifices efficiency for security, by passing communications requests through Hassan. The security structure also means that Hassan does not know the members of Anton's cells, and Kim may know only ways to communicate with them but not their identity.

Kim operates two systems of cells, one for secure communications and one for propaganda. To send out a propaganda message, Osama must pass it to Kim. If Kim were compromised, the core group might have significant problems with any sort of outside communications.

Terrorist networks do not match cleanly to other cell systems that regularly report to a headquarters. The apparent al-Qaeda methodology of letting operational cells decide on their final dates and means of attack exhibit an operational pattern, but not a periodicity that could easily be used for an [[Intelligence analysis management#Indications &amp; warning checklists|indications checklist]] appropriate for a warning center. Such lists depend on seeing a local pattern to give a specific warning.&lt;ref name=Vos&gt;{{cite web
 | title = Modeling Terrorist Networks - Complex Systems at the Mid-Range
 | first1 = Philip Vos
 | last1 = Fellman
 | first2 = Roxana
 | last2 = Wright
 | url = http://www.psych.lse.ac.uk/complexity/Conference/FellmanWright.pdf
 |format=PDF| accessdate = 2007-11-02
}}&lt;/ref&gt;

Note that Hassan has two subordinates that have not yet established operational cells. These subordinates can be considered '''sleepers''', but not necessarily with a sleeper cell.

===Operational cells===
For each mission are created one or more operational cells. If the al-Qaeda signature of multiple concurrent attacks is used, there may be an operational cell for each target location. It will depend on the operation if they will need any support cells in the operational area. For example, it may be more secure to have a local cell build bombs, which will be delivered by cells coming from outside the area.

"Operational cells are not created, but instead 'seeded' utilizing individuals spotted or that request assistance (both groups are 'vetted' by being trained under the observation of the core group, which dramatically restricts the opportunity for passing off walk-ins under false flag). Categorization of operational cells appears to be by capabilities, region, and then task/operation. Operational cells are composed of members whose worldview has been firmly tested—necessary to front-load, because such cells are dispersed back to their own local control (or negative control—proscribed behavior—with positive control only coming in the form of contact for synchronization or support)."&lt;ref name=Sleepers /&gt;

If operational cells routinely are "released" ''curved dotted lines on link to military cells'' to select their final operational parameters, they use a different paradigm than governmental clandestine or covert operations. On a number of cases, US special operations forces had to wait for Presidential authorization to make an attack, or even move to staging areas. Admittedly, a country would have to face the consequences of an inappropriate attack, so it may tend to be overcautious, where a terror network would merely shrug at the world being upset. Assuming that the al-Qaeda operational technique is not to use positive control, their operations may be more random, but also more unpredictable for counterterror forces. If their cells truly need constant control, there are communications links that might be detected by SIGINT, and if their command can be disrupted, the field units could not function. Since there is fairly little downside for terrorists to attack out of synchronization with other activities, the lack of positive control becomes a strength of their approach to cell organization.
[[Image:T-Cell-2.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

The operational cells need to have continuous internal communication; there is a commander, who may be in touch with infrastructure cells or, less likely from a security standpoint with the core group.

Al-Qaeda's approach, which even differs from that of earlier terrorist organizations, may be very viable for their goals:

* Cells are redundant and distributed, making them difficult to ‘roll up’
* Cells are coordinated, not under "command &amp; control"—this autonomy and local control makes them flexible, and enhances security
* Trust and comcon internally to the cell provide redundancy of potential command (a failure of Palestinian operations in the past), and well as a shared knowledgebase (which may mean, over time, that ‘cross training’ emerges inside a cell, providing redundancy of most critical skills and knowledge).&lt;ref name=Sleepers /&gt;

===Indirect support networks===
In the above graphic, note the indirect support network controlled by Richard's subcell.

"While Al-Qaida has elements of the organization designed to support the structure, but such elements are insufficient in meeting the needs of such an organization, and for security reasons there would be redundant and secondary-/tertiary-networks that are unaware of their connection to Al-Qaida. These networks, primarily related to fundraising and financial activities, as well as technology providers, are in a ‘use’ relationship with Al-Qaida—managed through cut-outs or individuals that do not inform them of the nature of activities, and that may have a cover pretext sufficient to deflect questions or inquiry."&lt;ref name=Sleepers /&gt;

===A possible countermeasure===
In 2002, ''U.S. News &amp; World Report'' said that American intelligence is beginning to acquire a sufficiently critical mass of intelligence on al-Qaida indicating, "Once thought nearly impossible to penetrate, al Qaeda is proving no tougher a target than the KGB or the Mafia--closed societies that took the U.S. government years to get inside. "We're getting names, the different camps they trained at, the hierarchy, the infighting," says an intelligence official. "It's very promising."&lt;ref name=Kaplan2002&gt;{{Cite journal
 | title = Run and Gun: Al Qaeda arrests and intelligence hauls bring new energy to the war on terrorism
 | first = David E. | last = Kaplan
 | date = 22 September 2002
 | journal = U.S. News &amp; World Report
 | url = http://www.usnews.com/usnews/news/articles/020930/archive_022824.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; The report also said that the collected data has allowed the recruiting of informants.

Writing in the U.S. Army journal ''Military Review'', David W. Pendall  suggested that a "catch-and-release program for suspected operatives might create reluctance or distrust in such suspects and prevent them from further acts or, perhaps more important, create distrust in the cell leaders of these individuals in the future." The author noted the press release describing Ramzi Binalshib's cooperation with the United States "are sure to prevent reentry into a terrorist cell as a trusted member and most likely limits the further trust and assignments of close cell associates still at large. The captor would determine when to name names and when to remain silent."&lt;ref name=Pendall2004&gt;{{Cite journal
 | date = January–February 2004
 | journal = Military Review
 | url = http://calldp.leavenworth.army.mil
 | first = David W. | last = Pendall
 | title =Effects-Based Operations and the Exercise of National Power
 | publisher = [[United States Army Combined Arms Center]]
 | postscript = &lt;!--None--&gt;
}}  Find the article by going through the Military Review directories&lt;/ref&gt; Indeed, once intelligence learns the name and characteristics of an at-large adversary, as well as some sensitive information that would plausibly be known to him, a news release could be issued to talk about his cooperation. Such a method could not be used too often, but, used carefully, could disturb the critical trust networks. The greatest uncertainty might be associated with throwing doubt onto a key member of an operational cell that has gone autonomous.

==See also==
* [[Leaderless resistance]]
* [[Lone wolf (terrorism)]]

==References==
{{reflist | 2}}

==External links==
* [http://theriskyshift.com/2012/06/an-introduction-to-terrorist-organisational-structures/ An Introduction To Terrorist Organisational Structures]

{{Intelligence cycle management}}

[[Category:Counter-intelligence]]
[[Category:Types of espionage]]
[[Category:Intelligence analysis]]
[[Category:Military intelligence]]
[[Category:Military tactics]]
[[Category:Secrecy]]
[[Category:Terrorism tactics]]</text>
    <sha1>e11a1287df4560d6fa9f7e71aee143dd3155e94a</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>:String</title>
  <ns>828</ns>
  <id>5</id>
  <revision>
    <id>5</id>
    <timestamp>2015-12-23T21:25:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{High-risk|2,600,000+}}  {{ml|module=string}}  This module is intended to provide access to basic string functions.  Most of the functions provided here can be invoked with n..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7994" xml:space="preserve">{{High-risk|2,600,000+}}

{{ml|module=string}}

This module is intended to provide access to basic string functions.

Most of the functions provided here can be invoked with named parameters, unnamed parameters, or a mixture.  If named parameters are used, Mediawiki will automatically remove any leading or trailing whitespace from the parameter. Depending on the intended use, it may be advantageous to either preserve or remove such whitespace.

== Global options ==

; ignore_errors
: If set to 'true' or 1, any error condition will result in an empty string being returned rather than an error message.
; error_category
: If an error occurs, specifies the name of a category to include with the error message.  The default category is [[:Category:Errors reported by Module String]].
; no_category
: If set to 'true' or 1, no category will be added if an error is generated.

Unit tests for this module are available at [[Module:String/testcases]].

== len ==

This function returns the length of the target string.

Usage:

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|len|''target_string''}}&lt;/code&gt;

OR

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|len|s= ''target_string'' }}&lt;/code&gt;

Parameters:

; s
: The string whose length to report

== sub ==

: This function returns a substring of the target string at specified indices.

Usage:

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|sub|''target_string''|''start_index''|''end_index''}}&lt;/code&gt;

OR

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|sub|s= ''target_string'' |i= ''start_index'' |j= ''end_index'' }}&lt;/code&gt;

Parameters:

; s
: The string to return a subset of
; i
: The first index of the substring to return, defaults to 1.
; j
: The last index of the string to return, defaults to the last character.

The first character of the string is assigned an index of 1.  If either i or j is a negative value, it is interpreted the same as selecting a character by counting from the end of the string.  Hence, a value of -1 is the same as selecting the last character of the string.

If the requested indices are out of range for the given string, an error is reported.

== sublength ==

This function implements the features of {{tl|Str sub old}} and is kept in order to maintain these older templates.

== match ==

This function returns a substring from the source string that matches a specified pattern.

Usage:

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|match|''source_string''|''pattern_string''|''start_index''|''match_number''|''plain_flag''|''nomatch_output''}}&lt;/code&gt;

OR

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|match|s= ''source_string'' |pattern= ''pattern_string'' |start= ''start_index''|match= ''match_number''|plain= ''plain_flag'' |nomatch= ''nomatch_output'' }}&lt;/code&gt;

Parameters:

; s
: The string to search
; pattern
: The pattern or string to find within the string
; start
: The index within the source string to start the search.  The first character of the string has index 1.  Defaults to 1.
; match
: In some cases it may be possible to make multiple matches on a single string.  This specifies which match to return, where the first match is match= 1.  If a negative number is specified then a match is returned counting from the last match.  Hence match = -1 is the same as requesting the last match.  Defaults to 1.
; plain
: A flag indicating that the pattern should be understood as plain text.  Defaults to false.
; nomatch
: If no match is found, output the "nomatch" value rather than an error.

If the match_number or start_index are out of range for the string being queried, then this function generates an error.  An error is also generated if no match is found.
If one adds the parameter ignore_errors=true, then the error will be suppressed and an empty string will be returned on any failure.

For information on constructing [[w:en:Lua (programming language)|Lua]] patterns, a form of [[w:en:regular expression|regular expression]], see:

* [[mw:Extension:Scribunto/Lua_reference_manual#Patterns|Scribunto patterns]]
* [[mw:Extension:Scribunto/Lua_reference_manual#Ustring_patterns|Scribunto Unicode string patterns]]

== pos ==

This function returns a single character from the target string at position pos.

Usage:

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|pos|''target_string''|''index_value''}}&lt;/code&gt;

OR

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|pos|target= ''target_string'' |pos= ''index_value'' }}&lt;/code&gt;

Parameters:

; target
: The string to search
; pos
: The index for the character to return

The first character has an index value of 1.

If one requests a negative value, this function will select a character by counting backwards
from the end of the string.  In other words pos = -1 is the same as asking for the last character.

A requested value of zero, or a value greater than the length of the string returns an error.

== str_find ==

This function duplicates the behavior of {{tl|str_find}}, including all of its quirks. This is provided in order to support existing templates, but is NOT RECOMMENDED for new code and templates.  New code is recommended to use the "find" function instead.

Returns the first index in "source" that is a match to "target".  Indexing is 1-based, and the function returns -1 if the "target" string is not present in "source".

Important Note: If the "target" string is empty / missing, this function returns a value of "1", which is generally unexpected behavior, and must be accounted for separatetly.

== find ==

This function allows one to search for a target string or pattern within another string.

Usage:

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|find|''source_str''|''target_string''|''start_index''|''plain_flag''}}&lt;/code&gt;

OR

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|find|source= ''source_str'' |target= ''target_str'' |start= ''start_index''|plain= ''plain_flag'' }}&lt;/code&gt;

Parameters:

; source
: The string to search
; target
: The string or pattern to find within source
; start
: The index within the source string to start the search, defaults to 1
; plain
: Boolean flag indicating that target should be understood as plain text and not as a [[w:en:Lua (programming language)|Lua]]-style [[w:en:regular expression|regular expression]], defaults to true

This function returns the first index &gt;= "start" where "target" can be found within "source".  Indices are 1-based.  If "target" is not found, then this function returns 0.  If either "source" or "target" are missing / empty, this function also returns 0.

This function should be safe for UTF-8 strings.

== replace ==

This function allows one to replace a target string or pattern within another string.

Usage:

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|replace|''source_str''|''pattern_string''|''replace_string''|''replacement_count''|''plain_flag''}}&lt;/code&gt;

OR

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|replace|source= ''source_string'' |pattern= ''pattern_string''|replace= ''replace_string'' |count= ''replacement_count'' |plain= ''plain_flag'' }}&lt;/code&gt;

Parameters:

; source
: The string to search
; pattern
: The string or pattern to find within source
; replace
: The replacement text
; count
: The number of occurrences to replace; defaults to all
; plain
: Boolean flag indicating that pattern should be understood as plain text and not as a [[mw:Extension:Scribunto/Lua reference manual#Ustring patterns|Scribunto ustring pattern]] (a unicode-friendly [[w:en:Lua (programming language)|Lua]]-style [[w:en:regular expression|regular expression]]); defaults to true

== rep ==

Repeats a string ''n'' times. A simple function to pipe string.rep to templates.
Usage:

: &lt;code&gt;&lt;nowiki&gt;{{#invoke:&lt;/nowiki&gt;String|rep|''source''|''count''}}&lt;/code&gt;

Parameters:

; source
: The string to repeat
; count
: The number of repetitions.

Example &lt;code&gt;&lt;nowiki&gt;{{#invoke:String|rep|hello|3}}&lt;/nowiki&gt;&lt;/code&gt; gives {{#invoke:String|rep|hello|3}}&lt;includeonly&gt;{{#ifeq:{{SUBPAGENAME}}|sandbox||

[[Category:Lua metamodules|String, {{PAGENAME}}]]

}}&lt;/includeonly&gt;</text>
    <sha1>aeadfc435482a98034a78c6fbd3428c4993a77d0</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>:String/testcases</title>
  <ns>828</ns>
  <id>6</id>
  <revision>
    <id>6</id>
    <timestamp>2015-12-23T21:29:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "local p = require('Module:UnitTests')   function p:test_len()     self:preprocess_equals_many('{{#invoke:String/sandbox|len|', '}}', {         {' foo ', '5'},         {'s= foo..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2727" xml:space="preserve">local p = require('Module:UnitTests')
 
function p:test_len()
    self:preprocess_equals_many('{{#invoke:String/sandbox|len|', '}}', {
        {' foo ', '5'},
        {'s= foo ', '3'},
        {'', '0'},
        {'s=', '0'},
        {'   ', '3'},
        {'最近の更新', '5'},
    })
end

function p:test_replace()
    self:preprocess_equals_many('{{#invoke:String/sandbox|replace|', '}}', {
        {'1.1.1.1|.|/', '1/1/1/1'},
        {'alpha (beta)| (| gamma (', 'alpha gamma (beta)'},
        {'Dog (cat)|%s%(.*%)||plain=false', 'Dog'},
    })
end

function p:test_match()
    self:preprocess_equals_many('{{#invoke:String/sandbox|match|', '}}', {
        {'dog (cat)|%((%a-)%)', 'cat'},
        {'dog (cat) (canary) (fish)|%((%a-)%)||-1', 'fish'},
        {'dog (cat) (canary) (fish)|%((%a-)%)||2', 'canary'},
        {'dog (cat) (canary) (fish)|%((%a-)%)|6|1', 'canary'},
        {'dog (cat) (canary) (fish)|%((%a-)%)|6|2', 'fish'},
        {'dog (cat)|%((%a-)%)||2|no_category=true', '&lt;strong class="error"&gt;String Module Error: Match not found&lt;/strong&gt;'},
        {'dog (cat)|%((%a-)%)||2|ignore_errors=true', ''},
    })
end
function p:test_match()
    self:preprocess_equals_many('{{#invoke:String/sandbox|match|', '}}', {
        {'dog (cat)|%((%a-)%)', 'cat'},
        {'dog (cat) (canary) (fish)|%((%a-)%)||-1', 'fish'},
        {'dog (cat) (canary) (fish)|%((%a-)%)||2', 'canary'},
        {'dog (cat) (canary) (fish)|%((%a-)%)|6|1', 'canary'},
        {'dog (cat) (canary) (fish)|%((%a-)%)|6|2', 'fish'},
        {'dog (cat)|%((%a-)%)||2|no_category=true', '&lt;strong class="error"&gt;String Module Error: Match not found&lt;/strong&gt;'},
        {'dog (cat)|%((%a-)%)||2|ignore_errors=true', ''},
    })
end

function p:test_find()
    self:preprocess_equals_many('{{#invoke:String/sandbox|find|', '}}', {
        {'', '0'},
        {'source=', '0'},
        {'source=|target=', '0'},
        {'source=|target=Bob', '0'},
        {'Bob|Joe', '0'},
        {'Bob|b', '3'},
        {'Bob Joe|oe', '6'},
        {'source= Bob |o', '2'},
        {' Bob |o', '3'},
        {'높지만 급격히|만', '3'},
        {'source=BAAAB|target=%w|plain=false', '1'},
        {'source=BAAAB|target=%w|start=3|plain=false', '3'},
        {'source=BAAAB|target=(%w)%1|plain=false', '2'},
    })
end

function p:test_rep()
    self:preprocess_equals_many('{{#invoke:String/sandbox|rep|', '}}', {
        {'abc|1', 'abc'},
        {'a b|7', 'a ba ba ba ba ba ba b'},
        {'bla|glug|no_category=true', '&lt;strong class="error"&gt;String Module Error: function rep expects a number as second parameter, received "glug"&lt;/strong&gt;'},
        {'bla|glug|ignore_errors=true', ''},
        {'àèò|3', 'àèòàèòàèò'}
    })
end

return p</text>
    <sha1>dcee5406dbfff66b0b94cef98554851ec273a9be</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:High-risk</title>
  <ns>10</ns>
  <id>7</id>
  <revision>
    <id>7</id>
    <timestamp>2015-12-23T21:38:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{ombox | type = content | image = [[File:Ambox warning orange.svg|40px|alt=|link=]] | text =  '''This {{ #switch:{{NAMESPACE}} |Module=Lua module |#default=template }} is use..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1443" xml:space="preserve">{{ombox
| type = content
| image = [[File:Ambox warning orange.svg|40px|alt=|link=]]
| text = 
'''This {{
#switch:{{NAMESPACE}}
|Module=Lua module
|#default=template
}} is used on &lt;span class="plainlinks"&gt;[http://tools.wmflabs.org/templatecount/index.php?lang=en&amp;namespace={{NAMESPACENUMBER:{{FULLPAGENAME}}}}&amp;name={{urlencode:{{PAGENAME}}}} {{#if:{{{1|}}}|{{formatnum:{{{1}}}}}|a very large number of}} pages].'''&lt;/span&gt;&lt;br /&gt;To avoid large-scale disruption and unnecessary server load, any changes to this {{
#switch:{{NAMESPACE}}
|Module=module
|#default=template
}} should first be tested in its [[{{
#switch: {{SUBPAGENAME}}
| doc | sandbox = {{SUBJECTSPACE}}:{{BASEPAGENAME}}
| #default      = {{SUBJECTPAGENAME}}
}}/sandbox|/sandbox]] or [[{{
#switch: {{SUBPAGENAME}}
| doc | sandbox = {{SUBJECTSPACE}}:{{BASEPAGENAME}}
| #default      = {{SUBJECTPAGENAME}}
}}/testcases|/testcases]] subpages{{
#switch:{{NAMESPACE}}
|Module=.
|#default=, or in your own [[Wikipedia:Subpages#How to create user subpages|user subpage]].
}} The tested changes can then be added to this page in one single edit. Please consider discussing any changes on {{#if:{{{2|}}}|[[{{{2}}}]]|the [[{{
#switch: {{SUBPAGENAME}}
| doc | sandbox = {{TALKSPACE}}:{{BASEPAGENAME}}
| #default      = {{TALKPAGENAME}}
}}|talk page]]}} before implementing them.
}}&lt;noinclude&gt;
{{Documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
    <sha1>812c9e1a01722157b734340923858c7f7717eed3</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Ombox</title>
  <ns>10</ns>
  <id>8</id>
  <revision>
    <id>8</id>
    <timestamp>2015-12-23T21:39:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{#invoke:Message box|ombox}}&lt;noinclude&gt; {{documentation}} &lt;!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --&gt; &lt;/noinclude"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="145" xml:space="preserve">{{#invoke:Message box|ombox}}&lt;noinclude&gt;
{{documentation}}
&lt;!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --&gt;
&lt;/noinclude</text>
    <sha1>f229f655ad42b3254e96c75d6dc0fa81f1a11412</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Ml</title>
  <ns>10</ns>
  <id>9</id>
  <revision>
    <id>9</id>
    <timestamp>2015-12-23T21:40:46Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;includeonly&gt;{{ml-multi|module={{{module|{{{1|}}}}}}|sandbox={{{sandbox|}}}}}&lt;/includeonly&gt;&lt;noinclude&gt; {{documentation}} &lt;/noinclude&gt;"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="133" xml:space="preserve">&lt;includeonly&gt;{{ml-multi|module={{{module|{{{1|}}}}}}|sandbox={{{sandbox|}}}}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>54c7fac4a1a0391ab03c25b62d72dae899d2c02b</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Ml-multi</title>
  <ns>10</ns>
  <id>10</id>
  <revision>
    <id>10</id>
    <timestamp>2015-12-23T21:41:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;span class="plainlinks"&gt;[[Module:{{{module|{{{1|}}}}}}]]&amp;nbsp;&lt;!--  --&gt;{{#if:{{{sup|}}} |&lt;sup&gt;}}&lt;!--  --&gt;{{Toolbar |style={{yesno|{{{small|yes}}}|yes=font-size:90%}} |separat..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="936" xml:space="preserve">&lt;span class="plainlinks"&gt;[[Module:{{{module|{{{1|}}}}}}]]&amp;nbsp;&lt;!--
 --&gt;{{#if:{{{sup|}}} |&lt;sup&gt;}}&lt;!--
 --&gt;{{Toolbar |style={{yesno|{{{small|yes}}}|yes=font-size:90%}} |separator={{{separator|dot}}}
     | 1 = [[:Module talk:{{{module|}}}|talk]]
     | 2 = {{edit|1=Module:{{{module|}}}|2=edit}}
     | 3 = {{history|Module:{{{module|}}}|hist}}
     | 4 = [{{fullurl:Special:WhatLinksHere/:Module:{{{module|}}}|limit=999}} links]
     | 5 = [[Module:{{{module|{{{1|}}}}}}/doc|doc]]
     | 6 = [[Special:PrefixIndex/Module:{{{module|}}}|subpages]]
     | 7 = [[Module:{{{module|}}}/testcases|tests]]&amp;nbsp;([[Module talk:{{{module|}}}/testcases|results]])
     | 8 = {{#if:{{{sandbox&lt;includeonly&gt;|&lt;/includeonly&gt;}}}
            | {{Ml-multi/sandboxlinks |module={{{module|{{{1|}}}}}} |project={{{project|}}} |sandbox={{{sandbox|}}} }}
    }}     }}&lt;!--
 --&gt;{{#if:{{{sup|}}} |&lt;/sup&gt;}}&lt;!--
--&gt;&lt;/span&gt;&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>7f316b30a42de662b1b9381f7c9853d8ebc680fb</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Reflist</title>
  <ns>10</ns>
  <id>11</id>
  <revision>
    <id>11</id>
    <timestamp>2015-12-23T21:45:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;div class="reflist &lt;!--  --&gt;{{#if: {{{1|}}}     | columns {{#iferror: {{#ifexpr: {{{1|1}}} &gt; 1 }}       | references-column-width        | references-column-count references-..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="817" xml:space="preserve">&lt;div class="reflist &lt;!--
 --&gt;{{#if: {{{1|}}}
    | columns {{#iferror: {{#ifexpr: {{{1|1}}} &gt; 1 }}
      | references-column-width 
      | references-column-count references-column-count-{{#if:1|{{{1}}}}} }}
    | {{#if: {{{colwidth|}}}
      | references-column-width }} }}" style="&lt;!--
 --&gt;{{#if: {{{1|}}}
    | {{#iferror: {{#ifexpr: {{{1|1}}} &gt; 1 }}
      | {{column-width|{{#if:1|{{{1}}}}}}}
      | {{column-count|{{#if:1|{{{1}}}}}}} }}
    | {{#if: {{{colwidth|}}}
      | {{column-width|{{{colwidth}}}}} }} }} list-style-type: &lt;!--
 --&gt;{{{liststyle|{{#switch: {{{group|}}}
    | upper-alpha
    | upper-roman
    | lower-alpha
    | lower-greek
    | lower-roman = {{{group}}}
    | #default = decimal}}}}};"&gt;
{{#tag:references|{{{refs|}}}|group={{{group|}}}}}&lt;/div&gt;&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>262fc11f5c62a7ad95b8d0d03383b362c2bb43b0</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>File:Wdip-Cell-0.png</title>
  <ns>6</ns>
  <id>12</id>
  <revision>
    <id>12</id>
    <timestamp>2015-12-23T21:55:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>File:Wnoc-Cell-0.png</title>
  <ns>6</ns>
  <id>13</id>
  <revision>
    <id>13</id>
    <timestamp>2015-12-23T21:57:56Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>File:Wnoc-Cell-1.png</title>
  <ns>6</ns>
  <id>14</id>
  <revision>
    <id>14</id>
    <timestamp>2015-12-23T21:59:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>File:T-Cell-0.png</title>
  <ns>6</ns>
  <id>15</id>
  <revision>
    <id>15</id>
    <timestamp>2015-12-23T22:00:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>File:T-Cell-1.png</title>
  <ns>6</ns>
  <id>16</id>
  <revision>
    <id>16</id>
    <timestamp>2015-12-23T22:00:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>File:T-Cell-2.png</title>
  <ns>6</ns>
  <id>17</id>
  <revision>
    <id>17</id>
    <timestamp>2015-12-23T22:01:43Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:For</title>
  <ns>10</ns>
  <id>18</id>
  <revision>
    <id>18</id>
    <timestamp>2015-12-23T22:04:47Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Hatnote|For {{#if:{{{1|}}}|{{{1}}}|other uses}}, see [[:{{{2|{{PAGENAME}} (disambiguation)}}}]]{{#if:{{{3|}}}|{{#if:{{{4|}}}|, [[:{{{3}}}]], {{#if:{{{5|}}}|[[:{{{4}}}]], and..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="280" xml:space="preserve">{{Hatnote|For {{#if:{{{1|}}}|{{{1}}}|other uses}}, see [[:{{{2|{{PAGENAME}} (disambiguation)}}}]]{{#if:{{{3|}}}|{{#if:{{{4|}}}|, [[:{{{3}}}]], {{#if:{{{5|}}}|[[:{{{4}}}]], and [[:{{{5}}}]]|and [[:{{{4}}}]]}}|&amp;#32;and [[:{{{3}}}]]}}}}.}}&lt;noinclude&gt;

{{Documentation}}

&lt;/noinclude&gt;</text>
    <sha1>c3931828e393f43a1a8d0da3ebde9254fd266463</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Hatnote</title>
  <ns>10</ns>
  <id>19</id>
  <revision>
    <id>19</id>
    <timestamp>2015-12-23T22:05:41Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Hatnote|For {{#if:{{{1|}}}|{{{1}}}|other uses}}, see [[:{{{2|{{PAGENAME}} (disambiguation)}}}]]{{#if:{{{3|}}}|{{#if:{{{4|}}}|, [[:{{{3}}}]], {{#if:{{{5|}}}|[[:{{{4}}}]], and..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="280" xml:space="preserve">{{Hatnote|For {{#if:{{{1|}}}|{{{1}}}|other uses}}, see [[:{{{2|{{PAGENAME}} (disambiguation)}}}]]{{#if:{{{3|}}}|{{#if:{{{4|}}}|, [[:{{{3}}}]], {{#if:{{{5|}}}|[[:{{{4}}}]], and [[:{{{5}}}]]|and [[:{{{4}}}]]}}|&amp;#32;and [[:{{{3}}}]]}}}}.}}&lt;noinclude&gt;

{{Documentation}}

&lt;/noinclude&gt;</text>
    <sha1>c3931828e393f43a1a8d0da3ebde9254fd266463</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Multiple issues</title>
  <ns>10</ns>
  <id>20</id>
  <revision>
    <id>20</id>
    <timestamp>2015-12-23T22:07:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Ambox |name  = Multiple issues |doc   = no |subst = &lt;includeonly&gt;{{subst:substcheck}}&lt;/includeonly&gt; |class = ambox-multiple_issues compact-ambox |type  = content |text  = &lt;t..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1049" xml:space="preserve">{{Ambox
|name  = Multiple issues
|doc   = no
|subst = &lt;includeonly&gt;{{subst:substcheck}}&lt;/includeonly&gt;
|class = ambox-multiple_issues compact-ambox
|type  = content
|text  = &lt;table class="collapsible  {{#ifeq:{{{collapsed}}}|yes|collapsed}}" style="width:95%; background:transparent;"&gt;
&lt;tr&gt;&lt;th style="text-align:left; padding:0.2em 2px 0.2em 0;"&gt; This {{#if:{{{section|}}}|section|article}} has multiple issues. &lt;span style="font-weight: normal;"&gt;Please help '''[{{fullurl:{{FULLPAGENAME}}|action=edit}} improve it]''' or discuss these issues on the '''[[{{TALKPAGENAME}}|talk page]]'''.&lt;/span&gt;&lt;/th&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;{{#invoke:String|replace|source={{{1|}}}|pattern=style="display: none"|replace=|count=}}
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
{{#ifeq:{{{2|a}}}|{{{2|b}}}|[[Category:Pages using multiple issues with incorrect parameters|§{{PAGENAME}}]]
}}{{#invoke:Check for unknown parameters|check|unknown=[[Category:Pages using multiple issues with incorrect parameters|_VALUE_{{PAGENAME}}]]
| collapsed | section | 1 | 2 }}
}}&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>fef905b904bc5a39ff609f6332e3d5198639c3fb</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>:Math</title>
  <ns>828</ns>
  <id>21</id>
  <revision>
    <id>21</id>
    <timestamp>2015-12-23T22:16:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "--[[  This module provides a number of basic mathematical operations.  ]]  local yesno, getArgs -- lazily initialized  local p = {} -- Holds functions to be returned from #inv..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12731" xml:space="preserve">--[[

This module provides a number of basic mathematical operations.

]]

local yesno, getArgs -- lazily initialized

local p = {} -- Holds functions to be returned from #invoke, and functions to make available to other Lua modules.
local wrap = {} -- Holds wrapper functions that process arguments from #invoke. These act as intemediary between functions meant for #invoke and functions meant for Lua.

--[[
Helper functions used to avoid redundant code.
]]

local function err(msg)
	-- Generates wikitext error messages.
	return mw.ustring.format('&lt;strong class="error"&gt;Formatting error: %s&lt;/strong&gt;', msg)
end

local function unpackNumberArgs(args)
	-- Returns an unpacked list of arguments specified with numerical keys.
	local ret = {}
	for k, v in pairs(args) do
		if type(k) == 'number' then
			table.insert(ret, v)
		end
	end
	return unpack(ret)
end

local function makeArgArray(...)
	-- Makes an array of arguments from a list of arguments that might include nils.
	local args = {...} -- Table of arguments. It might contain nils or non-number values, so we can't use ipairs.
	local nums = {} -- Stores the numbers of valid numerical arguments.
	local ret = {}
	for k, v in pairs(args) do
		v = p._cleanNumber(v)
		if v then
			nums[#nums + 1] = k
			args[k] = v
		end
	end
	table.sort(nums)
	for i, num in ipairs(nums) do
		ret[#ret + 1] = args[num]
	end
	return ret
end

local function applyFuncToArgs(func, ...)
	-- Use a function on all supplied arguments, and return the result. The function must accept two numbers as parameters,
	-- and must return a number as an output. This number is then supplied as input to the next function call.
	local vals = makeArgArray(...)	
	local count = #vals -- The number of valid arguments
	if count == 0 then return
		-- Exit if we have no valid args, otherwise removing the first arg would cause an error.
		nil, 0
	end 
	local ret = table.remove(vals, 1)
	for _, val in ipairs(vals) do
		ret = func(ret, val)
	end
	return ret, count
end

--[[
random

Generate a random number

Usage:
{{#invoke: Math | random }}
{{#invoke: Math | random | maximum value }}
{{#invoke: Math | random | minimum value | maximum value }}
]]

function wrap.random(args)
	local first = p._cleanNumber(args[1])
	local second = p._cleanNumber(args[2])
	return p._random(first, second)
end

function p._random(first, second)
	math.randomseed(mw.site.stats.edits + mw.site.stats.pages + os.time() + math.floor(os.clock() * 1000000000))
	-- math.random will throw an error if given an explicit nil parameter, so we need to use if statements to check the params.
	if first and second then
		if first &lt;= second then -- math.random doesn't allow the first number to be greater than the second.
			return math.random(first, second)
		end
	elseif first then
		return math.random(first)
	else
		return math.random()
	end
end

--[[
order

Determine order of magnitude of a number

Usage:
{{#invoke: Math | order | value }}
]]

function wrap.order(args)
	local input_string = (args[1] or args.x or '0');
	local input_number = p._cleanNumber(input_string);
	if input_number == nil then
		return err('order of magnitude input appears non-numeric')
	else
		return p._order(input_number)
	end    
end

function p._order(x)
	if x == 0 then return 0 end
	return math.floor(math.log10(math.abs(x)))
end

--[[
precision

Detemines the precision of a number using the string representation

Usage:
{{ #invoke: Math | precision | value }}
]]

function wrap.precision(args)
	local input_string = (args[1] or args.x or '0');
	local trap_fraction = args.check_fraction;
	local input_number;

	if not yesno then
		yesno = require('Module:Yesno')
	end
	if yesno(trap_fraction, true) then -- Returns true for all input except nil, false, "no", "n", "0" and a few others. See [[Module:Yesno]].
		local pos = string.find(input_string, '/', 1, true);
		if pos ~= nil then
			if string.find(input_string, '/', pos + 1, true) == nil then
				local denominator = string.sub(input_string, pos+1, -1);
				local denom_value = tonumber(denominator);
				if denom_value ~= nil then
					return math.log10(denom_value);
				end
			end                        
		end
	end    

	input_number, input_string = p._cleanNumber(input_string);
	if input_string == nil then
		return err('precision input appears non-numeric')
	else
		return p._precision(input_string)
	end    
end

function p._precision(x)
	if type(x) == 'number' then
		x = tostring(x)
	end
	x = string.upper(x)

	local decimal = x:find('%.')
	local exponent_pos = x:find('E')
	local result = 0;

	if exponent_pos ~= nil then
		local exponent = string.sub(x, exponent_pos + 1)
		x = string.sub(x, 1, exponent_pos - 1)
		result = result - tonumber(exponent)
	end    

	if decimal ~= nil then
		result = result + string.len(x) - decimal
		return result
	end

	local pos = string.len(x);
	while x:byte(pos) == string.byte('0') do
		pos = pos - 1
		result = result - 1
		if pos &lt;= 0 then
			return 0
		end
	end

	return result
end

--[[
max

Finds the maximum argument

Usage:
{{#invoke:Math| max | value1 | value2 | ... }}

Note, any values that do not evaluate to numbers are ignored.
]]

function wrap.max(args)
	return p._max(unpackNumberArgs(args))
end

function p._max(...)
	local function maxOfTwo(a, b)
		if a &gt; b then
			return a
		else
			return b
		end
	end
	local max_value = applyFuncToArgs(maxOfTwo, ...)
	if max_value then
		return max_value
	end
end

--[[
min 

Finds the minimum argument

Usage:
{{#invoke:Math| min | value1 | value2 | ... }}
OR
{{#invoke:Math| min }}

When used with no arguments, it takes its input from the parent
frame.  Note, any values that do not evaluate to numbers are ignored.
]]

function wrap.min(args)
	return p._min(unpackNumberArgs(args))
end

function p._min(...)
	local function minOfTwo(a, b)
		if a &lt; b then
			return a
		else
			return b
		end
	end
	local min_value = applyFuncToArgs(minOfTwo, ...)
	if min_value then
		return min_value
	end
end

--[[
average 

Finds the average

Usage:
{{#invoke:Math| average | value1 | value2 | ... }}
OR
{{#invoke:Math| average }}

Note, any values that do not evaluate to numbers are ignored.
]]

function wrap.average(args)
	return p._average(unpackNumberArgs(args))
end

function p._average(...)
	local function getSum(a, b)
		return a + b
	end
	local sum, count = applyFuncToArgs(getSum, ...)
	if not sum then
		return 0
	else
		return sum / count
	end
end

--[[
round

Rounds a number to specified precision

Usage:
{{#invoke:Math | round | value | precision }}

--]]

function wrap.round(args)
	local value = p._cleanNumber(args[1] or args.value or 0)
	local precision = p._cleanNumber(args[2] or args.precision or 0)
	if value == nil or precision == nil then
		return err('round input appears non-numeric')
	else
		return p._round(value, precision)
	end    
end

function p._round(value, precision)
	local rescale = math.pow(10, precision or 0);
	return math.floor(value * rescale + 0.5) / rescale;
end

--[[
mod

Implements the modulo operator

Usage:
{{#invoke:Math | mod | x | y }}

--]]

function wrap.mod(args)
	local x = p._cleanNumber(args[1])
	local y = p._cleanNumber(args[2])
	if not x then
		return err('first argument to mod appears non-numeric')
	elseif not y then
		return err('second argument to mod appears non-numeric')
	else
		return p._mod(x, y)
	end    
end

function p._mod(x, y)
	local ret = x % y
	if not (0 &lt;= ret and ret &lt; y) then
		ret = 0
	end
	return ret
end

--[[
gcd

Calculates the greatest common divisor of multiple numbers

Usage:
{{#invoke:Math | gcd | value 1 | value 2 | value 3 | ... }}
--]]

function wrap.gcd(args)
	return p._gcd(unpackNumberArgs(args))
end

function p._gcd(...)
	local function findGcd(a, b)
		local r = b
		local oldr = a
		while r ~= 0 do
			local quotient = math.floor(oldr / r)
			oldr, r = r, oldr - quotient * r
		end
		if oldr &lt; 0 then
			oldr = oldr * -1
		end
		return oldr
	end
	local result, count = applyFuncToArgs(findGcd, ...)
	return result
end

--[[
precision_format

Rounds a number to the specified precision and formats according to rules 
originally used for {{template:Rnd}}.  Output is a string.

Usage:
{{#invoke: Math | precision_format | number | precision }}
]]

function wrap.precision_format(args)
	local value_string = args[1] or 0
	local precision = args[2] or 0
	return p._precision_format(value_string, precision)
end

function p._precision_format(value_string, precision)
	-- For access to Mediawiki built-in formatter.
	local lang = mw.getContentLanguage();

	local value
	value, value_string = p._cleanNumber(value_string)
	precision = p._cleanNumber(precision)

	-- Check for non-numeric input
	if value == nil or precision == nil then
		return err('invalid input when rounding')
	end

	local current_precision = p._precision(value)
	local order = p._order(value)

	-- Due to round-off effects it is neccesary to limit the returned precision under
	-- some circumstances because the terminal digits will be inaccurately reported.
	if order + precision &gt;= 14 then
		orig_precision = p._precision(value_string)
		if order + orig_precision &gt;= 14 then
			precision = 13 - order;        
		end        
	end

	-- If rounding off, truncate extra digits
	if precision &lt; current_precision then
		value = p._round(value, precision)
		current_precision = p._precision(value)
	end    

	local formatted_num = lang:formatNum(math.abs(value))
	local sign

	-- Use proper unary minus sign rather than ASCII default
	if value &lt; 0 then
		sign = '−'
	else
		sign = ''
	end    

	-- Handle cases requiring scientific notation
	if string.find(formatted_num, 'E', 1, true) ~= nil or math.abs(order) &gt;= 9 then
		value = value * math.pow(10, -order)
		current_precision = current_precision + order
		precision = precision + order
		formatted_num = lang:formatNum(math.abs(value))
	else
		order = 0;        
	end
	formatted_num = sign .. formatted_num

	-- Pad with zeros, if needed    
	if current_precision &lt; precision then
		local padding
		if current_precision &lt;= 0 then
			if precision &gt; 0 then
				local zero_sep = lang:formatNum(1.1)
				formatted_num = formatted_num .. zero_sep:sub(2,2)

				padding = precision
				if padding &gt; 20 then
					padding = 20
				end

				formatted_num = formatted_num .. string.rep('0', padding)
			end            
		else                   
			padding = precision - current_precision
			if padding &gt; 20 then
				padding = 20
			end
			formatted_num = formatted_num .. string.rep('0', padding)
		end
	end

	-- Add exponential notation, if necessary.
	if order ~= 0 then
		-- Use proper unary minus sign rather than ASCII default
		if order &lt; 0 then
			order = '−' .. lang:formatNum(math.abs(order))
		else
			order = lang:formatNum(order)
		end    

		formatted_num = formatted_num .. '&lt;span style="margin:0 .15em 0 .25em"&gt;×&lt;/span&gt;10&lt;sup&gt;' .. order .. '&lt;/sup&gt;'
	end

	return formatted_num
end

--[[
Helper function that interprets the input numerically.  If the 
input does not appear to be a number, attempts evaluating it as
a parser functions expression.
]]

function p._cleanNumber(number_string)
	if type(number_string) == 'number' then
		-- We were passed a number, so we don't need to do any processing.
		return number_string, tostring(number_string)
	elseif type(number_string) ~= 'string' or not number_string:find('%S') then
		-- We were passed a non-string or a blank string, so exit.
		return nil, nil;
	end

	-- Attempt basic conversion
	local number = tonumber(number_string)

	-- If failed, attempt to evaluate input as an expression
	if number == nil then
		local success, result = pcall(mw.ext.ParserFunctions.expr, number_string)
		if success then
			number = tonumber(result)
			number_string = tostring(number)
		else
			number = nil
			number_string = nil
		end
	else
		number_string = number_string:match("^%s*(.-)%s*$") -- String is valid but may contain padding, clean it.
		number_string = number_string:match("^%+(.*)$") or number_string -- Trim any leading + signs.
		if number_string:find('^%-?0[xX]') then
			-- Number is using 0xnnn notation to indicate base 16; use the number that Lua detected instead.
			number_string = tostring(number)
		end
	end

	return number, number_string
end

--[[
Wrapper function that does basic argument processing. This ensures that all functions from #invoke can use either the current
frame or the parent frame, and it also trims whitespace for all arguments and removes blank arguments.
]]

local mt = { __index = function(t, k)
	return function(frame)
		if not getArgs then
			getArgs = require('Module:Arguments').getArgs
		end
		return wrap[k](getArgs(frame))  -- Argument processing is left to Module:Arguments. Whitespace is trimmed and blank arguments are removed.
	end
end }

return setmetatable(p, mt)</text>
    <sha1>d19d14a98e92fe25b60a9b87561498b620889504</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>:Random</title>
  <ns>828</ns>
  <id>22</id>
  <revision>
    <id>22</id>
    <timestamp>2015-12-23T22:19:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "-- This module contains a number of functions that make use of random numbers.  local cfg = {}  -------------------------------------------------------------------------------..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12855" xml:space="preserve">-- This module contains a number of functions that make use of random numbers.

local cfg = {}

--------------------------------------------------------------------------------------
-- Configuration
--------------------------------------------------------------------------------------

-- Set this to true if your wiki has a traffic rate of less than one edit every two minutes or so.
-- This will prevent the same "random" number being generated many times in a row until a new edit is made
-- to the wiki. This setting is only relevant if the |same= parameter is set.
cfg.lowTraffic = false

-- If cfg.lowTraffic is set to true, and the |same= parameter is set, this value is used for the refresh rate of the random seed.
-- This is the number of seconds until the seed is changed. Getting this right is tricky. If you set it too high, the same number
-- will be returned many times in a row. If you set it too low, you may get different random numbers appearing on the same page,
-- particularly for pages that take many seconds to process.
cfg.seedRefreshRate = 60

--------------------------------------------------------------------------------------
-- End configuration
--------------------------------------------------------------------------------------

local p = {} -- For functions available from other Lua modules.
local l = {} -- For functions not available from other Lua modules, but that need to be accessed using table keys.

local yesno = require('Module:Yesno')
local makeList = require('Module:List').makeList

--------------------------------------------------------------------------------------
-- Helper functions
--------------------------------------------------------------------------------------

local function raiseError(msg)
	-- This helps to generate a wikitext error. It is the calling function's responsibility as to how to include it in the output.
	return mw.ustring.format('&lt;b class="error"&gt;[[Module:Random]] error: %s.&lt;/b&gt;', msg)
end

--------------------------------------------------------------------------------------
-- random number function
--------------------------------------------------------------------------------------

local function getBigRandom(l, u)
	-- Gets a random integer between l and u, and is not limited to RAND_MAX.
	local r = 0
	local n = 2^math.random(30) -- Any power of 2.
	local limit = math.ceil(53 / (math.log(n) / math.log(2)))
	for i = 1, limit do
		r = r + math.random(0, n - 1) / (n^i)
	end
	return math.floor(r * (u - l + 1)) + l
end

function l.number(args)
	-- Gets a random number.
	first = tonumber(args[1])
	second = tonumber(args[2])
	-- This needs to use if statements as math.random won't accept explicit nil values as arguments.
	if first then
		if second then
			if first &gt; second then -- Second number cannot be less than the first, or it causes an error.
				first, second = second, first
			end
			return getBigRandom(first, second)
		else
			return getBigRandom(1, first)
		end
	else
		return math.random()
	end
end

--------------------------------------------------------------------------------------
-- Date function
--------------------------------------------------------------------------------------

function l.date(args)
	-- This function gets random dates, and takes timestamps as positional arguments.
	-- With no arguments specified, it outputs a random date in the current year.
	-- With two arguments specified, it outputs a random date between the timestamps.
	-- With one argument specified, the date is a random date between the unix epoch (1 Jan 1970) and the timestamp.
	-- The output can be formatted using the "format" argument, which works in the same way as the #time parser function.
	-- The default format is the standard Wikipedia timestamp.
	local lang = mw.language.getContentLanguage()

	local function getDate(format, ts)
		local success, date = pcall(lang.formatDate, lang, format, ts)
		if success then
			return date
		end
	end

	local function getUnixTimestamp(ts)
		local unixts = getDate('U', ts)
		if unixts then
			return tonumber(unixts)
		end
	end

	local t1 = args[1]
	local t2 = args[2]
	
	-- Find the start timestamp and the end timestamp.
	local startTimestamp, endTimestamp
	if not t1 then
		-- Find the first and last second in the current year.
		local currentYear = tonumber(getDate('Y'))
		local currentYearStartUnix = tonumber(getUnixTimestamp('1 Jan ' .. tostring(currentYear)))
		local currentYearEndUnix = tonumber(getUnixTimestamp('1 Jan ' .. tostring(currentYear + 1))) - 1
		startTimestamp = '@' .. tostring(currentYearStartUnix) -- @ is used to denote Unix timestamps with lang:formatDate.
		endTimestamp = '@' .. tostring(currentYearEndUnix)
	elseif t1 and not t2 then
		startTimestamp = '@0' -- the Unix epoch, 1 January 1970
		endTimestamp = t1
	elseif t1 and t2 then
		startTimestamp = t1
		endTimestamp = t2
	end

	-- Get Unix timestamps and return errors for bad input (or for bugs in the underlying PHP library, of which there are unfortunately a few)
	local startTimestampUnix = getUnixTimestamp(startTimestamp)
	local endTimestampUnix = getUnixTimestamp(endTimestamp)
	if not startTimestampUnix then
		return raiseError('"' .. tostring(startTimestamp) .. '" was not recognised as a valid timestamp')
	elseif not endTimestampUnix then
		return raiseError('"' .. tostring(endTimestamp) .. '" was not recognised as a valid timestamp')
	elseif startTimestampUnix &gt; endTimestampUnix then
		return raiseError('the start date must not be later than the end date (start date: "' .. startTimestamp .. '", end date: "' .. endTimestamp .. '")')
	end

	-- Get a random number between the two Unix timestamps and return it using the specified format.
	local randomTimestamp = getBigRandom(startTimestampUnix, endTimestampUnix)
	local dateFormat = args.format or 'H:i, d F Y (T)'
	local result = getDate(dateFormat, '@' .. tostring(randomTimestamp))
	if result then
		return result
	else
		return raiseError('"' .. dateFormat .. '" is not a valid date format')
	end
end

--------------------------------------------------------------------------------------
-- List functions
--------------------------------------------------------------------------------------

local function randomizeArray(t, limit)
	-- Randomizes an array. It works by iterating through the list backwards, each time swapping the entry
	-- "i" with a random entry. Courtesy of Xinhuan at http://forums.wowace.com/showthread.php?p=279756
	-- If the limit parameter is set, the array is shortened to that many elements after being randomized.
	-- The lowest possible value is 0, and the highest possible is the length of the array.
	local len = #t
	for i = len, 2, -1 do
		local r = math.random(i)
		t[i], t[r] = t[r], t[i]
	end
	if limit and limit &lt; len then
		local ret = {}
		for i, v in ipairs(t) do
			if i &gt; limit then
				break
			end
			ret[i] = v
		end
		return ret
	else
		return t
	end
end

local function removeBlanks(t)
	-- Removes blank entries from an array so that it can be used with ipairs.
	local ret = {}
	for k, v in pairs(t) do
		if type(k) == 'number' then
			table.insert(ret, k)
		end
	end
	table.sort(ret)
	for i, v in ipairs(ret) do
		ret[i] = t[v]
	end
	return ret
end

local function makeSeparator(sep)
	if sep == 'space' then
		-- Include an easy way to use spaces as separators.
		return ' '
	elseif sep == 'newline' then
		-- Ditto for newlines
		return '\n'
	elseif type(sep) == 'string' then
		-- If the separator is a recognised MediaWiki separator, use that. Otherwise use the value of sep if it is a string.
		local mwseparators = {'dot', 'pipe', 'comma', 'tpt-languages'}
		for _, mwsep in ipairs(mwseparators) do
			if sep == mwsep then
				return mw.message.new( sep .. '-separator' ):plain()
			end
		end
		return sep
	end
end

local function makeRandomList(args)
	local list = removeBlanks(args)
	list = randomizeArray(list, tonumber(args.limit))
	return list
end

function l.item(args)
	-- Returns a random item from a numbered list.
	local list = removeBlanks(args)
	local len = #list
	if len &gt;= 1 then
		return list[math.random(len)]
	end
end

function l.list(args)
	-- Randomizes a list and concatenates the result with a separator.
	local list = makeRandomList(args)
	local sep = makeSeparator(args.sep or args.separator)
	return table.concat(list, sep)
end

function l.text_list(args)
	-- Randomizes a list and concatenates the result, text-style. Accepts separator and conjunction arguments.
	local list = makeRandomList(args)
	local sep = makeSeparator(args.sep or args.separator)
	local conj = makeSeparator(args.conj or args.conjunction)
	return mw.text.listToText(list, sep, conj)
end

function l.array(args)
	-- Returns a Lua array, randomized. For use from other Lua modules.
	return randomizeArray(args.t, args.limit)
end

--------------------------------------------------------------------------------------
-- HTML list function
--------------------------------------------------------------------------------------

function l.html_list(args, listType)
	-- Randomizes a list and turns it into an HTML list. Uses [[Module:List]].
	listType = listType or 'bulleted'
	local listArgs = makeRandomList(args) -- Arguments for [[Module:List]].
	for k, v in pairs(args) do
		if type(k) == 'string' then
			listArgs[k] = v
		end
	end
	return makeList(listType, listArgs)
end

--------------------------------------------------------------------------------------
-- The main function. Called from other Lua modules.
--------------------------------------------------------------------------------------

function p.main(funcName, args, listType)
	-- Sets the seed for the random number generator and passes control over to the other functions.
	local same = yesno(args.same)
	if not same then
		-- Generates a different number every time the module is called, even from the same page.
		-- This is because of the variability of os.clock (the time in seconds that the Lua script has been running for).
		math.randomseed(mw.site.stats.edits + mw.site.stats.pages + os.time() + math.floor(os.clock() * 1000000000))
	else
		if not cfg.lowTraffic then
			-- Make the seed as random as possible without using anything time-based. This means that the same random number
			-- will be generated for the same input from the same page - necessary behaviour for some wikicode templates that
			-- assume bad pseudo-random-number generation.
			local stats = mw.site.stats
			local views = stats.views or 0 -- This is not always available, so we need a backup.
			local seed = views + stats.pages + stats.articles + stats.files + stats.edits + stats.users + stats.activeUsers + stats.admins -- Make this as random as possible without using os.time() or os.clock()
			math.randomseed(seed)
		else
			-- Make the random seed change every n seconds, where n is set by cfg.seedRefreshRate.
			-- This is useful for low-traffic wikis where new edits may not happen very often.
			math.randomseed(math.floor(os.time() / cfg.seedRefreshRate))
		end
	end
	if type(args) ~= 'table' then
		error('the second argument to p.main must be a table')
	end
	return l[funcName](args, listType)
end
	
--------------------------------------------------------------------------------------
-- Process arguments from #invoke
--------------------------------------------------------------------------------------

local function makeWrapper(funcName, listType)
	-- This function provides a wrapper for argument-processing from #invoke.
	-- listType is only used with p.html_list, and is nil the rest of the time.
	return function (frame)
		-- If called via #invoke, use the args passed into the invoking template, or the args passed to #invoke if any exist.
		-- Otherwise assume args are being passed directly in from the debug console or from another Lua module.
		local origArgs
		if frame == mw.getCurrentFrame() then
			origArgs = frame:getParent().args
			for k, v in pairs(frame.args) do
				origArgs = frame.args
				break
			end
		else
			origArgs = frame
		end
		-- Trim whitespace and remove blank arguments.
		local args = {}
		for k, v in pairs(origArgs) do
			if type(v) == 'string' then
				v = mw.text.trim(v)
			end
			if v ~= '' then
				args[k] = v
			end
		end
		return p.main(funcName, args, listType)
	end
end

-- Process arguments for HTML list functions.
local htmlListFuncs = {
	bulleted_list           = 'bulleted',
	unbulleted_list         = 'unbulleted',
	horizontal_list         = 'horizontal',
	ordered_list            = 'ordered',
	horizontal_ordered_list = 'horizontal_ordered'
}
for funcName, listType in pairs(htmlListFuncs) do
	p[funcName] = makeWrapper('html_list', listType)
end

-- Process arguments for other functions.
local otherFuncs = {'number', 'date', 'item', 'list', 'text_list'}
for _, funcName in ipairs(otherFuncs) do
	p[funcName] = makeWrapper(funcName)
end

return p</text>
    <sha1>ee35eaddf353b9f1503193207f6eade28db3c086</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>:List</title>
  <ns>828</ns>
  <id>23</id>
  <revision>
    <id>23</id>
    <timestamp>2015-12-23T22:20:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "-- This module outputs different kinds of lists. At the moment, bulleted, -- unbulleted, horizontal, ordered, and horizontal ordered lists are supported.  local libUtil = requ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5138" xml:space="preserve">-- This module outputs different kinds of lists. At the moment, bulleted,
-- unbulleted, horizontal, ordered, and horizontal ordered lists are supported.

local libUtil = require('libraryUtil')
local checkType = libUtil.checkType
local mTableTools = require('Module:TableTools')

local p = {}

local listTypes = {
	['bulleted'] = true,
	['unbulleted'] = true,
	['horizontal'] = true,
	['ordered'] = true,
	['horizontal_ordered'] = true
}

function p.makeListData(listType, args)
	-- Constructs a data table to be passed to p.renderList.
	local data = {}

	-- Classes
	data.classes = {}
	if listType == 'horizontal' or listType == 'horizontal_ordered' then
		table.insert(data.classes, 'hlist')
	elseif listType == 'unbulleted' then
		table.insert(data.classes, 'plainlist')
	end
	table.insert(data.classes, args.class)

	-- Main div style
	data.style = args.style

	-- Indent for horizontal lists
	if listType == 'horizontal' or listType == 'horizontal_ordered' then
		local indent = tonumber(args.indent)
		indent = indent and indent * 1.6 or 0
		if indent &gt; 0 then
			data.marginLeft = indent .. 'em'
		end
	end
	
	-- List style types for ordered lists
	-- This could be "1, 2, 3", "a, b, c", or a number of others. The list style
	-- type is either set by the "type" attribute or the "list-style-type" CSS
	-- property.
	if listType == 'ordered' or listType == 'horizontal_ordered' then 
		data.listStyleType = args.list_style_type or args['list-style-type']
		data.type = args['type']

		-- Detect invalid type attributes and attempt to convert them to
		-- list-style-type CSS properties.
		if data.type 
			and not data.listStyleType
			and not tostring(data.type):find('^%s*[1AaIi]%s*$')
		then
			data.listStyleType = data.type
			data.type = nil
		end
	end
	
	-- List tag type
	if listType == 'ordered' or listType == 'horizontal_ordered' then
		data.listTag = 'ol'
	else
		data.listTag = 'ul'
	end

	-- Start number for ordered lists
	data.start = args.start
	if listType == 'horizontal_ordered' then
		-- Apply fix to get start numbers working with horizontal ordered lists.
		local startNum = tonumber(data.start)
		if startNum then
			data.counterReset = 'listitem ' .. tostring(startNum - 1)
		end
	end

	-- List style
	 -- ul_style and ol_style are included for backwards compatibility. No
	 -- distinction is made for ordered or unordered lists.
	data.listStyle = args.list_style

	-- List items
	-- li_style is included for backwards compatibility. item_style was included
	-- to be easier to understand for non-coders.
	data.itemStyle = args.item_style or args.li_style
	data.items = {}
	for i, num in ipairs(mTableTools.numKeys(args)) do
		local item = {}
		item.content = args[num]
		item.style = args['item' .. tostring(num) .. '_style']
			or args['item_style' .. tostring(num)]
		item.value = args['item' .. tostring(num) .. '_value']
			or args['item_value' .. tostring(num)]
		table.insert(data.items, item)
	end
	
	return data
end

function p.renderList(data)
	-- Renders the list HTML.
	
	-- Return the blank string if there are no list items.
	if type(data.items) ~= 'table' or #data.items &lt; 1 then
		return ''
	end
	
	-- Render the main div tag.
	local root = mw.html.create('div')
	for i, class in ipairs(data.classes or {}) do
		root:addClass(class)
	end
	root:css{['margin-left'] = data.marginLeft}
	if data.style then
		root:cssText(data.style)
	end

	-- Render the list tag.
	local list = root:tag(data.listTag or 'ul')
	list
		:attr{start = data.start, type = data.type}
		:css{
			['counter-reset'] = data.counterReset,
			['list-style-type'] = data.listStyleType
		}
	if data.listStyle then
		list:cssText(data.listStyle)
	end

	-- Render the list items
	for i, t in ipairs(data.items or {}) do
		local item = list:tag('li')
		if data.itemStyle then
			item:cssText(data.itemStyle)
		end
		if t.style then
			item:cssText(t.style)
		end
		item
			:attr{value = t.value}
			:wikitext(t.content)
	end

	return tostring(root)
end

function p.renderTrackingCategories(args)
	local isDeprecated = false -- Tracks deprecated parameters.
	for k, v in pairs(args) do
		k = tostring(k)
		if k:find('^item_style%d+$') or k:find('^item_value%d+$') then
			isDeprecated = true
			break
		end
	end
	local ret = ''
	if isDeprecated then
		ret = ret .. '[[Category:List templates with deprecated parameters]]'
	end
	return ret
end

function p.makeList(listType, args)
	if not listType or not listTypes[listType] then
		error(string.format(
			"bad argument #1 to 'makeList' ('%s' is not a valid list type)",
			tostring(listType)
		), 2)
	end
	checkType('makeList', 2, args, 'table')
	local data = p.makeListData(listType, args)
	local list = p.renderList(data)
	local trackingCategories = p.renderTrackingCategories(args)
	return list .. trackingCategories
end

for listType in pairs(listTypes) do
	p[listType] = function (frame)
		local mArguments = require('Module:Arguments')
		local origArgs = mArguments.getArgs(frame)
		-- Copy all the arguments to a new table, for faster indexing.
		local args = {}
		for k, v in pairs(origArgs) do
			args[k] = v
		end
		return p.makeList(listType, args)
	end
end

return p</text>
    <sha1>913ea46e6c4b4825b443da53158be6d6260b349d</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Tl</title>
  <ns>10</ns>
  <id>24</id>
  <revision>
    <id>24</id>
    <timestamp>2015-12-23T22:42:32Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&amp;#123;&amp;#123;[[Template:{{{1}}}|{{{1}}}]]&amp;#125;&amp;#125;&lt;noinclude&gt; {{documentation}} &lt;!-- Categories go on the /doc subpage and interwikis go on Wikidata. --&gt; &lt;/noinclude&gt;"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="168" xml:space="preserve">&amp;#123;&amp;#123;[[Template:{{{1}}}|{{{1}}}]]&amp;#125;&amp;#125;&lt;noinclude&gt;
{{documentation}}
&lt;!-- Categories go on the /doc subpage and interwikis go on Wikidata. --&gt;
&lt;/noinclude&gt;</text>
    <sha1>91be693cd63410db06fc933eddb412ba433564dc</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Meeting Minutes/Files</title>
  <ns>10</ns>
  <id>25</id>
  <revision>
    <id>25</id>
    <timestamp>2015-12-24T15:36:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Meeting Minutes/Files" template. It should be called in the following format: &lt;pre&gt; {{Meeting Minutes/Files }} &lt;/pre&gt; Edit the page to see the templat..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="246" xml:space="preserve">&lt;noinclude&gt;
This is the "Meeting Minutes/Files" template.
It should be called in the following format:
&lt;pre&gt;
{{Meeting Minutes/Files
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>54217178b983b76607d84aa804ce1b68824b297e</sha1>
  </revision>
  <revision>
    <id>26</id>
    <parentid>25</parentid>
    <timestamp>2015-12-24T15:37:41Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="76" xml:space="preserve">* {{File link | file={{{File or URL|}}} | alt={{{Alternate name|}}} }}&lt;br /&gt;</text>
    <sha1>e3aaacc900ef1de1f5c2c00650719a884d8ada8d</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:File link</title>
  <ns>10</ns>
  <id>26</id>
  <revision>
    <id>27</id>
    <timestamp>2015-12-24T15:40:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt;'''Template:File link''' is an alternate method of linking to files in this wiki. It allows all file linking, both to local wiki files and external files, to be per..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2636" xml:space="preserve">&lt;noinclude&gt;'''Template:File link''' is an alternate method of linking to files in this wiki. It allows all file linking, both to local wiki files and external files, to be performed with one method. See '''[[Help:Linking to files]]''' for a tutorial.

== Local Files ==
For local files use the format below. Note that the "alt" parameter is optional.
&lt;pre&gt;
{{File link | file=File:International Space Station.pdf | alt=ISS Presentation }} (note, this file has to exist for it to display properly)
&lt;/pre&gt;

The above wikitext displays as {{File link | file=File:International Space Station.pdf | alt=ISS Presentation }}. Note the "file info" link. There has been confusion with some wiki users who click on file links which bring them to another wiki page instead of directly to the file. Using this method, the major link will bring them directly to the file, whereas the "file info" link will bring them to the page where they can see the file upload history and upload new versions of the file.

If the local file does not exist, the output will look like {{File link | file=File:My Fictitious File.doc | alt=Alt name won't show }} 

== External Files ==
For external files use the format below. Make sure to include &lt;nowiki&gt;http://&lt;/nowiki&gt; or &lt;nowiki&gt;https://&lt;/nowiki&gt; at the beginning of the URL. Again the "alt" parameter is optional, but it will look ugly without it in this case.
&lt;pre&gt;
{{File link | file=http://example.com/somefile.pdf | alt=My File }}
&lt;/pre&gt;

The above wikitext displays as {{File link | file=http://example.com/somefile.pdf | alt=My File }}. Note that there is no "file info" link, since the EVA Wiki has no such info for external files.

&lt;/noinclude&gt;&lt;includeonly&gt;&lt;!-- 

    #
    #  DETERMINES if the filename is a local file or an external file
    #    #pos returns 0 if "File:" is found at the beginning of the string
    #    returns nothing if "File:" is not found in the string, or a number other than zero if found later in the string
    #
--&gt;{{#ifeq: 0 
    | {{#pos:{{{file}}}|File:}} | &lt;!-- 
 

    #
    #  if filename starts with "File:"
    #  
--&gt;&lt;span style="white-space:nowrap;"&gt;{{#ifexist:{{{file}}}&lt;!--

        --&gt;|[[Media:{{#replace:{{{file}}}|File:}}|{{#if: {{{alt|}}} | {{{alt}}} | {{#replace:{{{file}}}|File:}} }}]]&lt;sup&gt; &lt;nowiki&gt;[&lt;/nowiki&gt;[[:{{{file}}}|file info]]&lt;nowiki&gt;]&lt;/nowiki&gt;&lt;/sup&gt;|&lt;!--

        --&gt;[[{{{file}}}]]}}&lt;/span&gt;|&lt;!-- 


    #
    #  If does not start with "File:"
    #  NOTE: the #if statement trims whitespace off of the URL...stupid hack
    #  
--&gt;[{{#if:{{{file|}}}|{{{file|}}} }} {{{alt|}}}]&lt;!--


    #
    #  Close out ifeq function
    #
--&gt;}}&lt;/includeonly&gt;</text>
    <sha1>f01abbf6a0c0035ca11e3fe9ea554b946eb5ede8</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>File:Sitcen.jpg</title>
  <ns>6</ns>
  <id>27</id>
  <revision>
    <id>28</id>
    <timestamp>2015-12-24T15:48:04Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Category:Title Icon Category</title>
  <ns>14</ns>
  <id>29</id>
  <revision>
    <id>30</id>
    <timestamp>2015-12-24T20:24:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This is the Title Icon Category category."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="41" xml:space="preserve">This is the Title Icon Category category.</text>
    <sha1>f9840688d1bb0cc7979982d2f13cdd86233c66f7</sha1>
  </revision>
  <revision>
    <id>31</id>
    <parentid>30</parentid>
    <timestamp>2015-12-24T20:27:56Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="142" xml:space="preserve">This category sets a value for [[Property:Title Icon]]. 
{{#set: Title Icon=Framework.png}}&lt;noinclude&gt;[[Category:Framework Pages]]&lt;/noinclude&gt;</text>
    <sha1>7fec597f4401371f6c0b948a309ebc3f57c3d1e3</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Property:Title Icon</title>
  <ns>102</ns>
  <id>30</id>
  <revision>
    <id>32</id>
    <timestamp>2015-12-24T20:28:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This is a property of type [[Has type::Text]]. [[Category:Framework Pages]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>File:Framework.png</title>
  <ns>6</ns>
  <id>31</id>
  <revision>
    <id>33</id>
    <timestamp>2015-12-24T20:31:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Category:Framework Pages</title>
  <ns>14</ns>
  <id>32</id>
  <revision>
    <id>34</id>
    <timestamp>2015-12-24T20:32:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Framework Pages __HIDDENCAT__"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="29" xml:space="preserve">Framework Pages
__HIDDENCAT__</text>
    <sha1>c2c086712a5b10017084f7d5d0d461e5aa2658fd</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Meeting</title>
  <ns>10</ns>
  <id>33</id>
  <revision>
    <id>35</id>
    <timestamp>2015-12-24T21:19:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Meeting" template. It should be called in the following format: &lt;pre&gt; {{Meeting }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;include..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="218" xml:space="preserve">&lt;noinclude&gt;
This is the "Meeting" template.
It should be called in the following format:
&lt;pre&gt;
{{Meeting
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>cb388a6f63ac0705d3c3daaf098f99547cd2b17c</sha1>
  </revision>
  <revision>
    <id>36</id>
    <parentid>35</parentid>
    <timestamp>2015-12-24T21:19:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2994" xml:space="preserve">&lt;includeonly&gt;&lt;!--
# Template:Meeting
#   (1) Setup JS/CSS and category
#   (2) Add category
#   (3) Create wrapper div around infobox and table of contents
#   (4) Create infobox
#   (5) Close out wrapper div
#   (6) Show overview of meeting
#   (7) #ask query for recent meetings
#   (8) Show link to form
#   (9) Template documentation (noinclude)


#
# (1) Call the #meetingminutestemplate parser function in order to add
#     the required javascript and CSS to the meeting template (uses same
#     parser function as Template:Meeting minutes.
#
--&gt;{{#meetingminutestemplate:}}&lt;!--


#
# (2) Add Category:Meeting Minutes.
#
--&gt;[[Category:Meeting]]&lt;!--


#
# (3) Add wrapper &lt;div&gt; which will go around infobox and table of contents.
#     This allows the infobox and TOC to both be positioned on the left and
#     be approximately the same size. FIXME: make them exactly the same size
#
--&gt;&lt;div id="ext-meeting-minutes-toc-wrapper"&gt;&lt;!--


#
# (4) Create infobox
#
--&gt;
{| class="meeting-minutes-infobox"
! style="text-align: center; background-color:#ccccff;" colspan="2" |&lt;big&gt;{{PAGENAME}}&lt;/big&gt;
|-
! Standard day
| {{#if: {{{Standard day|}}} | [[Standard day::{{{Standard day|}}}]] | }}
|-
! Standard time
| {{#if: {{{Standard time|}}} | [[Standard time::{{{Standard time|}}}]] | }}
|-
! Building
| {{#if: {{{Building|}}} | [[Building::{{{Building|}}}]] | }}
|-
! Room
| {{#if: {{{Room|}}} | [[Room::{{{Room|}}}]] | }}
|-
! Call-in number
| {{#if: {{{Call-in number|}}} | [[Call in number::{{{Call-in number|}}}]] | }}
|-
! Call-in password
| {{#if: {{{Call-in password|}}} | [[Call in password::{{{Call-in password|}}}]] | }}
|-
! Managed by cadre(s)
| {{#arraymap:{{{Managed by cadre(s)|}}}|,|x|[[Managed by cadre::x]]}}
|-
! Notable attendee(s)
| {{#arraymap:{{{Notable attendee(s)|}}}|,|x|[[Notable attendee::User:x]]}}
|}
&lt;!--

#
# Note: no TOC in Template:Meeting at this time. could add __TOC__ here if desired.
#


#
# (5) Close out &lt;div&gt; wrapper around infobox and TOC
#
--&gt;&lt;/div&gt;&lt;!--


#
# (6) Show overview of meeting
#
--&gt;{{#if: {{{Overview|}}} | {{{Overview}}}{{#set: Overview ={{{Overview}}} }} | &lt;!-- else do nothing --&gt; }}&lt;!--


#
# (7) Perform #ask query to show recent meetings
#
--&gt;&lt;h2&gt;Recent Meetings&lt;/h2&gt;
{{#ask: [[Category:Meeting Minutes]] [[Meeting type::{{PAGENAME}}]]
| ?Meeting date = Date
| ?Notes taken by
| sort = Meeting date
| order = desc
| limit = 10
| default = No meetings of this type have been added
}}

&lt;!-- leave blank lines above


#
# (8) Add link to meeting minutes form
#
--&gt;[[Special:FormEdit/Meeting Minutes|Add Meeting Minutes]]&lt;!--


#
# (9) Template definition complete. Template documentation below (within noinclude).
#
--&gt;&lt;/includeonly&gt;&lt;noinclude&gt;
This is the "Meeting" template.
It should be called in the following format:
&lt;pre&gt;
{{Meeting
|Standard day=
|Standard time=
|Building=
|Room=
|Call-in number=
|Call-in password=
|Managed by cadre(s)=
|Notable attendee(s)=
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;</text>
    <sha1>9cc8140e41e6d05bf68a2d7c6d3fab0495676280</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Form:Meeting Minutes</title>
  <ns>106</ns>
  <id>34</id>
  <revision>
    <id>37</id>
    <timestamp>2015-12-24T21:20:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Meeting Minutes" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1165" xml:space="preserve">&lt;noinclude&gt;
This is the "Meeting Minutes" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=Meeting Minutes}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Meeting}}}
{| class="formtable"
! Standard day: 
| {{{field|Standard day}}}
|-
! Standard time: 
| {{{field|Standard time}}}
|-
! Building: 
| {{{field|Building}}}
|-
! Room: 
| {{{field|Room}}}
|-
! Call-in number: 
| {{{field|Call-in number}}}
|-
! Call-in password: 
| {{{field|Call-in password}}}
|-
! Managed by cadre(s): 
| {{{field|Managed by cadre(s)}}}
|-
! Notable attendee(s): 
| {{{field|Notable attendee(s)}}}
|-
! Overview: 
| {{{field|Overview}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>ea6987463ddf4aae900a9f59d159315f686f76c8</sha1>
  </revision>
  <revision>
    <id>38</id>
    <parentid>37</parentid>
    <timestamp>2015-12-24T21:21:06Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4664" xml:space="preserve">&lt;includeonly&gt;{{#meetingminutesform:}}__NOTOC__{{{info|page name=&lt;Meeting minutes[Meeting type]&gt; - &lt;Meeting minutes[Meeting date]&gt;}}}
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Meeting minutes}}}&lt;!--


Main Form Definition

--&gt;
&lt;div class="meeting-minutes-save-often"&gt;
&lt;h3&gt;Remember...&lt;/h3&gt;
'''[[Help:Save Often|Save often]]''' or '''[[Help:Text Editor|use a text editor]]'''. Revisions are free. Also, if there is ''anything'' you don't know how to do, see the '''[[Help:Meeting Minutes|help page]]''' for more info.
&lt;/div&gt;

&lt;h2&gt;Meeting Details&lt;/h2&gt;
&lt;div class="meeting-minutes-edit-section multipleTemplateInstance"&gt;
{| class="formtable meeting-minutes-formtable"
! Meeting name
| {{{field|Meeting type|input type=combobox|values from category=Meeting|mandatory}}}
|-
! Meeting date
| {{{field|Meeting date|mandatory}}}
|-
! Start time
| {{{field|Start time hour|maxlength=2|input type=text|size=2|mandatory}}} : {{{field|Start time minute|maxlength=2|input type=text|size=2|mandatory}}} (24-hour time, please)
|-
! Notes taken by
| {{{field|Notes taken by|input type=text with autocomplete|values from namespace=User|mandatory|class=meeting-minutes-author-field}}}
|}
&lt;/div&gt;

&lt;h2&gt;Meeting Files&lt;/h2&gt;
{{{field|Meeting files|holds template}}}&lt;!-- 


--&gt;&lt;h1 style="margin-top:30px;"&gt;Meeting Topics&lt;/h1&gt;

{{{field|Topics|holds template}}}

{{{end template}}}&lt;!--


    Topics

--&gt;{{{for template|Topic from meeting|multiple|embed in field=Meeting minutes[Topics]|add button text=Add Topic}}}&lt;div class="instance-wrapper"&gt;
{{{field|Has topic title|class=full-width no-links-allowed title-input-field|placeholder=Topic Title}}}

{{{field|Related article|list|class=full-width no-links-allowed|input type=text with autocomplete|values from namespace=Main|placeholder=Related articles}}}

{{{field|Full text|input type=textarea|autogrow|class=full-width shrink-on-blur emphasize meeting-topic-full-text|cols=75}}}
&lt;/div&gt;{{{end template}}}&lt;!--


    Meeting Files (uploads and external files)

--&gt;{{{for template|Meeting Minutes/Files|multiple|embed in field=Meeting minutes[Meeting files]|add button text=Add File}}}
&lt;div class="mti-help-box mti-hide-on-blur"&gt;
Local files must be uploaded first. See [[Help:Meeting Minutes|the help page]] for more info.
&lt;/div&gt;
{| class="formtable meeting-minutes-formtable"
! Local File Name or URL
| {{{field|File or URL|class=full-width no-links-allowed|placeholder=Enter filename starting with File: or URL starting with http}}}
|-
! Alternate name
| {{{field|Alternate name|class=full-width no-links-allowed}}}
|}
{{{end template}}}&lt;!--

--&gt;
== Free text ==
{{Collapsible
  | Content =
* '''Use this field ''very'' sparingly'''
* Nothing in this field will be distributed to related pages
* Info in this field will be added to the end of the meeting minutes page
{{{standard input|free text|rows=10}}}
  | Collapse text = Hide Free Text
  | Expand text = Show Free Text Entry
  | Start hidden = true
}}

== Save Page ==
{{Collapsible
  | Content =
* '''Summary:''' Not required, but recommended if making a revision to a page. The summary will be included emails sent to people watching this page.
* '''Minor edit checkbox:''' Not required
* '''Watch this page checkbox:''' Check this box. If you are editing this page, in all likelihood you care about the content. Watch the page to have greater visibility into future changes. You can make it so the box is automatically checked by editing your preferences (top right of the screen). For more info see [[Help:Watching Pages]].
* '''Save page:''' Click this when you're done to save the page.
* '''Show preview:''' Click this to see what your wiki-markup will look like when formatted. Very handy for learning how to use the wiki.
* '''Show changes:''' Shows all changes you've made, compared to the previous revision (doesn't do much when creating a brand new page).
* '''Cancel:''' Don't click this unless you want to lose what you've been working on.
  | Collapse text = Hide Help
  | Expand text = Show Help
  | Start hidden = true
}}

{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;&lt;!--


  Below is content only shown on the Form:Meeting Minutes page

--&gt;&lt;noinclude&gt;
This is the "Meeting Minutes" form. Click edit to make changes to the structure of the form itself. Or [[Special:FormEdit/Meeting_Minutes|create new meeting minutes]].&lt;!--{{#forminput:form=Meeting Minutes}}--&gt;&lt;/noinclude&gt;</text>
    <sha1>ed1a0526883e36ac0732abd9754a0c025ef09f77</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Meeting Minutes Block</title>
  <ns>10</ns>
  <id>35</id>
  <revision>
    <id>39</id>
    <timestamp>2015-12-24T21:24:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Meeting Minutes Block" template. It should be called in the following format: &lt;pre&gt; {{Meeting Minutes Block }} &lt;/pre&gt; Edit the page to see the templat..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="246" xml:space="preserve">&lt;noinclude&gt;
This is the "Meeting Minutes Block" template.
It should be called in the following format:
&lt;pre&gt;
{{Meeting Minutes Block
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>9b42a32d937ad3943122655f1ee6f7894b30311b</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Template:Meeting topic and synopsis bullet</title>
  <ns>10</ns>
  <id>36</id>
  <revision>
    <id>40</id>
    <timestamp>2015-12-24T21:25:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Template:Meeting topic and synopsis bullet" template. It should be called in the following format: &lt;pre&gt; {{Template:Meeting topic and synopsis bullet..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="288" xml:space="preserve">&lt;noinclude&gt;
This is the "Template:Meeting topic and synopsis bullet" template.
It should be called in the following format:
&lt;pre&gt;
{{Template:Meeting topic and synopsis bullet
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>2e99a272b2644037b72d0c115813e046c3452271</sha1>
  </revision>
  <revision>
    <id>41</id>
    <parentid>40</parentid>
    <timestamp>2015-12-24T21:25:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="241" xml:space="preserve">&lt;noinclude&gt;
&lt;pre&gt;
{{{1|}}} = topic title
{{{2|}}} = synopsis
{{{3|}}} = From page
&lt;/pre&gt;
&lt;/noinclude&gt;&lt;includeonly&gt;* '''{{{1|}}}:''' {{{2|}}} {{#ifeq:{{Ends with|{{{2|}}}|...}}|true|&lt;small&gt;'''''[[{{{3|}}}|more]]'''''&lt;/small&gt;|}}
&lt;/includeonly&gt;</text>
    <sha1>582535fd28a9d3b06d8cf2d35c31ef94ce7490a0</sha1>
  </revision>
</page>
<page arvcontinue="20150907152945|263">
  <title>Template:Meeting Minutes Block info for table row</title>
  <ns>10</ns>
  <id>37</id>
  <revision>
    <id>42</id>
    <timestamp>2015-12-24T21:26:06Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Meeting Minutes Block info for table row" template. It should be called in the following format: &lt;pre&gt; {{Meeting Minutes Block info for table row }} &lt;..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="284" xml:space="preserve">&lt;noinclude&gt;
This is the "Meeting Minutes Block info for table row" template.
It should be called in the following format:
&lt;pre&gt;
{{Meeting Minutes Block info for table row
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>91cc4c5c4906462e3367d15d35518e85bb891a00</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>Template:Meeting Minutes Block info for table row</title>
  <ns>10</ns>
  <id>37</id>
  <revision>
    <id>43</id>
    <parentid>42</parentid>
    <timestamp>2015-12-24T21:26:31Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="696" xml:space="preserve">&lt;noinclude&gt;
&lt;pre&gt;
{{{1|}}} = Meeting page title (i.e. {{PAGENAME}} for meeting)
{{{2|}}} = Meeting type (Tools Panel, FIAR Call, etc...not full name of page like "EVA Tools Panel - 23 August 2012")
{{{3|}}} = Meeting date
&lt;/pre&gt;
&lt;/noinclude&gt;&lt;includeonly&gt;&lt;tr&gt;&lt;td&gt;&lt;table class="main-page-meeting-minutes-row" style="width:100%;padding:5px;border:1px solid #cccccc;margin:10px 0px 0px 0px;"&gt;&lt;tr&gt;&lt;th&gt;'''[[{{{1|}}}|{{{2|}}}]]''' ({{{3|}}})&lt;/th&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;{{#ask: [[Has topic title::+]][[From page::{{{1|}}}]]
|mainlabel=-
|? Has topic title
|? Synopsis
|? From page
|sort=Index
|link=none
|format = template
|template = Meeting topic and synopsis bullet
}}&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/includeonly&gt;</text>
    <sha1>1a3eb6dcece75f69b975e1622d52f57534c5fe0d</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>File:Network-300x226.jpg</title>
  <ns>6</ns>
  <id>38</id>
  <revision>
    <id>44</id>
    <timestamp>2015-12-25T02:59:47Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>45</id>
    <parentid>1</parentid>
    <timestamp>2015-12-25T03:04:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Replaced content with "== Reachback == [[File:Network-300x226.jpg|thumbnail]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="54" xml:space="preserve">== Reachback ==
[[File:Network-300x226.jpg|thumbnail]]</text>
    <sha1>fbbc4e6bd2d874dc1dcf5cba496bf20f0567805b</sha1>
  </revision>
  <revision>
    <id>46</id>
    <parentid>45</parentid>
    <timestamp>2015-12-25T03:06:03Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="72" xml:space="preserve">__NOEDITSECTION__
'''Reachback'''
[[File:Network-300x226.jpg|thumbnail]]</text>
    <sha1>1348ea1c4fe47c091e893d8c00654c78432ef1e1</sha1>
  </revision>
  <revision>
    <id>47</id>
    <parentid>46</parentid>
    <timestamp>2015-12-25T03:06:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="79" xml:space="preserve">__NOEDITSECTION__
'''Reachback'''
&lt;br /&gt;
[[File:Network-300x226.jpg|thumbnail]]</text>
    <sha1>e069600586ccf3141396b27717ace86f9257482b</sha1>
  </revision>
  <revision>
    <id>48</id>
    <parentid>47</parentid>
    <timestamp>2015-12-25T03:09:33Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="92" xml:space="preserve">__NOEDITSECTION__
'''Reachback'''
&lt;br /&gt;
[[File:Network-300x226.jpg|220px|thumbnail|link= ]]</text>
    <sha1>5e1a09384db275e91ed895e4de7ed9f1784f62f7</sha1>
  </revision>
  <revision>
    <id>52</id>
    <parentid>48</parentid>
    <timestamp>2015-12-26T22:45:47Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="80" xml:space="preserve">__NOEDITSECTION__
'''Reachback'''
&lt;br /&gt;
[[File:Multiple-Feeds.png|framed|left]]</text>
    <sha1>e6d2cb7d8cbc5cdbdfb4537beda154a9078e26d4</sha1>
  </revision>
  <revision>
    <id>53</id>
    <parentid>52</parentid>
    <timestamp>2015-12-26T22:47:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="87" xml:space="preserve">__NOEDITSECTION__
'''Reachback'''
&lt;br /&gt;
[[File:Multiple feeds.png|framed|left|link= ]]</text>
    <sha1>3ca313794cb8d1ce932894fcda90ffb13f379bb1</sha1>
  </revision>
  <revision>
    <id>54</id>
    <parentid>53</parentid>
    <timestamp>2015-12-26T22:48:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="85" xml:space="preserve">__NOEDITSECTION__
'''Reachback'''
&lt;br /&gt;
[[File:Multiple Feeds.png|thumbnail|link= ]]</text>
    <sha1>e1e9f0675b5e60fd2a21d3f34a4891fbfd78d35f</sha1>
  </revision>
  <revision>
    <id>55</id>
    <parentid>54</parentid>
    <timestamp>2015-12-26T22:50:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="91" xml:space="preserve">__NOEDITSECTION__
'''Reachback'''
&lt;br /&gt;
[[File:Multiple Feeds.png|right|thumbnail|link= ]]</text>
    <sha1>13271a683242ed58ecc7ead5d0a9d61616c87b70</sha1>
  </revision>
  <revision>
    <id>56</id>
    <parentid>55</parentid>
    <timestamp>2015-12-26T22:50:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="90" xml:space="preserve">__NOEDITSECTION__
'''Reachback'''
&lt;br /&gt;
[[File:Multiple Feeds.png|left|thumbnail|link= ]]</text>
    <sha1>f6754e853489733572882b575b271dfa3a0ccc6c</sha1>
  </revision>
  <revision>
    <id>57</id>
    <parentid>56</parentid>
    <timestamp>2015-12-26T22:51:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="87" xml:space="preserve">__NOEDITSECTION__
'''Reachback'''
&lt;br /&gt;
[[File:Multiple Feeds.png|left|framed|link= ]]</text>
    <sha1>8b7ec5081294629c9b499fe7283d87c3d36d510b</sha1>
  </revision>
  <revision>
    <id>58</id>
    <parentid>57</parentid>
    <timestamp>2015-12-26T22:51:41Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="90" xml:space="preserve">__NOEDITSECTION__
'''Reachback'''
&lt;br /&gt;
[[File:Multiple Feeds.png|left|frameless|link= ]]</text>
    <sha1>ca26ef99338b9e054e3ef52970f9bed18356d0f0</sha1>
  </revision>
  <revision>
    <id>59</id>
    <parentid>58</parentid>
    <timestamp>2015-12-26T22:52:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="67" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]</text>
    <sha1>21c96901eafa0e4982352fa58e52f05476d2cf92</sha1>
  </revision>
  <revision>
    <id>76</id>
    <parentid>59</parentid>
    <timestamp>2015-12-27T00:29:43Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="127" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=target.png}}</text>
    <sha1>9b83b8800bec128729d0e3fed1c8db25a409fc2c</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>File:Multiple Feeds.png</title>
  <ns>6</ns>
  <id>39</id>
  <revision>
    <id>49</id>
    <timestamp>2015-12-26T02:03:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>MediaWiki:Common.css</title>
  <ns>8</ns>
  <id>40</id>
  <revision>
    <id>50</id>
    <timestamp>2015-12-26T11:09:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "/* CSS placed here will be applied to all skins */  /* MediaWiki overrides */ /* body.page-Main_Page h1.firstHeading { display:none; } */ #footer-info { display: none; } /* Hi..."</comment>
    <model>css</model>
    <format>text/css</format>
    <text bytes="5386" xml:space="preserve">/* CSS placed here will be applied to all skins */

/* MediaWiki overrides */
/* body.page-Main_Page h1.firstHeading { display:none; } */
#footer-info { display: none; } /* Hide footer */
li#ca-talk { display: none; } /* Hide discussion tab */
#pt-login { display: none; } /* Hide login text */
#p-tb { display: none; } /* Hide toolbox */
/* #ca-history { display: none; } /* Hide "View history" */


/* Elements */
code { background: none; font: 10pt courier,serif; }
h2 { margin-top: 15px; }
h3 { color: #222; font-size: 11pt; margin: 10px 0 -5px; }
ol img { display: block; margin: 10px 10px 20px; }
ol li {  }
p  { margin-top: 10px; }
pre { background: #efefef; border: none; font: 10pt courier,serif; margin: 15px 0; padding: 10px; }
tt { font-size: 10pt; }

/* Controls */
.searchButton { background: #eee; border: 1px solid #ccc; color: #333; font: bold 8pt sans-serif; height: 20px; }

/* Boxes */
.fullbox { border: 1px solid #ccc; margin:5px; }
.title { background: #e8f2f8; border: none; border-bottom: 1px solid #ccc; color: #0e3793; font: bold 14pt sans-serif; margin: 0; padding: 5px; }
.subtitle { font: bold 10pt sans-serif; }
.example { background: #efefef; display: block; margin: 15px 0; padding: 10px; }

/* Formatting */
.clear { clear: both; }
.code { font: 10pt courier,serif; }
.hash { color: #090; }
.content { padding: 10px; }

/* Special elements */
div#kx-linkbar img { margin-right: 20px; }


.row {min-width:90% !important;}
.toctoggle {display:none}

table.wikitable &gt; tr &gt; th, 
table.wikitable &gt; tr &gt;td, 
table.wikitable &gt; * &gt; tr &gt;th, 
table.wikitable &gt; * &gt; tr &gt; td {
padding: 1px;
}
/*
div#viki_0{
width:100% !important;
}*/
.vikijs-detail-panel {
border:none !important;
background:white !important;
font-size:90%;
}
.vikijs-graph-container {
border:none !important;
}
.smwtable .row-even {
	background-color:#FFF;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
.smwtable .row-odd .stripe {
	background-color:#f0f7f8;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
h3#tagline {display:none; }
#footer-privacy {display:none}
#footer-disclaimer {display:none}
#footer-about {display:none}
#footer-lastmod {font-size:70%;}
#footer-viewcount {font-size:70%;}

p.title {
color:#009933;
font-size:100%;
}
h2 {
 font-size:125%;
}

h5 {
color: #666666;
}
.mw-search-formheader  {display:none; }
.thumbinner {
padding-left:5px;
padding-top:5px;
padding-bottom:5px;
}
.thumbcaption {
font-size:100%;
color:#009933;
background: white;
text-align: center;
}

h4 {
color:#009933;
}

form#sfForm.createbox, .formtable, table.formtable tr {
 background-color:#F0F8FF  !important;
}
form#sfForm.createbox, table.formtable tbody tr td table {
border: 1px solid #F0F8FF  !important;
}
option {
    font-weight:normal;
   font-size: x-small;
}
.createboxInput {
       background-color:#FFFFFF  !important;
}
.navbar-item {
	color: white !important;
	font-weight: bold;
	padding-top: 9px;
	padding-right: 10px;
}
.title {
	color:#009933;
        text-align: left;
        font-size:150%;
}

.top-bar,
.top-bar-section ul,
.top-bar-section ul li.active &gt; a,
.top-bar-section li a:not(.button),
.top-bar-section .has-form {
background:#061734;
font-size:90%;
color: #FFFFFF;
}

.top-bar-section &gt; ul &gt; .divider,
.top-bar-section &gt; ul &gt; [role="separator"] {
  border-color: #164eaf;
}

/* Darker color for the hover over items */
.top-bar-section ul li.hover &gt; a,
.top-bar-section ul li ul.dropdown li.hover &gt; a{
    background: #113e8c;
}

/* Slightly darker color for the dropdowns*/ 
.top-bar-section ul li ul.dropdown li &gt; a {
    background: #061734;
}
.spacer {
        height: 30px;
}
.np {
        height: 15px;
}
.hierarchyText {
        font-size:80%;
        font-weight:bold;
        height: 20px;
}
.hierarchyText table tbody tr  {
       background-color: #d5f99b;
       border: 1px solid #BFE08B;
       height: 20px;
}

.examplebread table tbody tr {
 background-color: #ADDFFF;
}

.citationtable {
	border: solid 1px #BBBBBB;
}

.citationtable td {
	padding-left: 5px;
	padding-right: 5px;
	max-width: 600px;
}
.citationtablelong td {
	padding-left: 5px;
	padding-right: 5px;
}

.itemtable td {
	vertical-align: top;
	min-width: 200px;
}

.ratingselected a {
	font-weight: bold;
	color: orange !important;
}

.nowrap {
	white-space: nowrap;
}
.filtered-filters { 
    float: left;
    width: 30%;
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    background: transparent;
}

.filtered-filters .filtered-value .filtered-value-option {
    display: block !important;
    width: 90% !important;
    padding: 0 !important;
}
 
.filtered-views { 
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    max-height: 800px;
}
 
.filtered-views .filtered-list { 
    width: 95% !important;
}
 
.filter_name {
    width: 150px;
    background:#96aab2;
    color:black;
    text-align:left;
    align:left;
    border:1px solid #ddd;
    padding: 3px;
}
 
.filter_value {
    width: 400px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.filter_icon {
    width: 50px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.top-bar.expanded .title-area {
   background:#164eaf;
}</text>
    <sha1>415b0e66372f8ec98fff3c44fb2b82385d376ed4</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>MediaWiki:Sidebar</title>
  <ns>8</ns>
  <id>41</id>
  <revision>
    <id>51</id>
    <timestamp>2015-12-26T11:31:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with " * navigation ** mainpage|mainpage-description ** helppage|help * SEARCH * TOOLBOX * LANGUAGES"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="94" xml:space="preserve">
* navigation
** mainpage|mainpage-description
** helppage|help
* SEARCH
* TOOLBOX
* LANGUAGES</text>
    <sha1>62efb54c1c76f7bfb77fafa741b67679b637f753</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>MediaWiki:Mainpage</title>
  <ns>8</ns>
  <id>42</id>
  <revision>
    <id>60</id>
    <timestamp>2015-12-26T22:58:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Reachback Operations"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">Reachback Operations</text>
    <sha1>3d85bfa9802f24e97b6a8e8a5f6c999fc392f9ce</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>Reachback Operations</title>
  <ns>0</ns>
  <id>43</id>
  <revision>
    <id>61</id>
    <timestamp>2015-12-26T23:04:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "__NOEDITSECTION__ [[File:Multiple Feeds.png|left|frameless|link= ]]   [[Related to::Information Operations]] {{#set:Name={{PAGENAME}}}}  {{DISPLAYTITLE: Reachback Operations}}"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="175" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


[[Related to::Information Operations]]
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}</text>
    <sha1>edd01fe335fbf34a8f1f68e0f532a9bef9e25268</sha1>
  </revision>
  <revision>
    <id>63</id>
    <parentid>61</parentid>
    <timestamp>2015-12-26T23:05:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="175" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{{Related to::Information Operations}}
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}</text>
    <sha1>9605545ad0a33be4250ef911331b49ed5d9ff823</sha1>
  </revision>
  <revision>
    <id>64</id>
    <parentid>63</parentid>
    <timestamp>2015-12-26T23:07:17Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="176" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
[[Related to::Information Operations]]</text>
    <sha1>e97013e3e33609bbea833f24633bb2985f427a03</sha1>
  </revision>
  <revision>
    <id>65</id>
    <parentid>64</parentid>
    <timestamp>2015-12-26T23:19:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="303" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
[[Related to::Information Operations]]
{{#set:Title Icon={{PAGENAME}}.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>a688108c2054e15f8ae43c38bcef3690f5ca1e4b</sha1>
  </revision>
  <revision>
    <id>66</id>
    <parentid>65</parentid>
    <timestamp>2015-12-26T23:20:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="264" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon={{PAGENAME}}.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>fc0bb73cccec406043dae8549d61867364890a27</sha1>
  </revision>
  <revision>
    <id>74</id>
    <parentid>66</parentid>
    <timestamp>2015-12-26T23:33:01Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[Reachback Operations]] to [[Reachback Support Operations]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="264" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon={{PAGENAME}}.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>fc0bb73cccec406043dae8549d61867364890a27</sha1>
  </revision>
  <revision>
    <id>77</id>
    <parentid>74</parentid>
    <timestamp>2015-12-27T00:41:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="261" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Support}}
{{#set:Title Icon={{PAGENAME}}.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>ed49ba3281b68ce27cbaa2f2fa041055def4c696</sha1>
  </revision>
  <revision>
    <id>79</id>
    <parentid>77</parentid>
    <timestamp>2015-12-27T00:43:31Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="256" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Support}}
{{#set:Title Icon=semwiki.jpg}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>cffe8c0d28af386598f79226d73de8d56705002b</sha1>
  </revision>
  <revision>
    <id>82</id>
    <parentid>79</parentid>
    <timestamp>2015-12-27T00:49:47Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="260" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Support}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>e79e12a9da957b8372ee100af169eab0c62200c7</sha1>
  </revision>
  <revision>
    <id>91</id>
    <parentid>82</parentid>
    <timestamp>2015-12-27T05:21:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[Reachback Support Operations]] to [[Reachback Operations]] over a redirect without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="260" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Support}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>e79e12a9da957b8372ee100af169eab0c62200c7</sha1>
  </revision>
  <revision>
    <id>92</id>
    <parentid>91</parentid>
    <timestamp>2015-12-27T05:22:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="263" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>aef711c440627ddaf0aac3bf6c2570d4ad474381</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>Property:Information Operations</title>
  <ns>102</ns>
  <id>44</id>
  <revision>
    <id>62</id>
    <timestamp>2015-12-26T23:05:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Page]].</text>
    <sha1>a77920a9d24db1d24320cdd74718a3bf351bd0c9</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>File:Reachback Operations.png</title>
  <ns>6</ns>
  <id>45</id>
  <revision>
    <id>67</id>
    <timestamp>2015-12-26T23:23:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>68</id>
    <parentid>67</parentid>
    <timestamp>2015-12-26T23:24:32Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[File:Operations.png]] to [[File:Reachback Operations.png]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>Property:Name</title>
  <ns>102</ns>
  <id>46</id>
  <revision>
    <id>69</id>
    <timestamp>2015-12-26T23:26:45Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
  <revision>
    <id>70</id>
    <parentid>69</parentid>
    <timestamp>2015-12-26T23:27:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47" xml:space="preserve">This is a property of type [[Has type::String]]</text>
    <sha1>7e2c6f7066c8ebe862e43dd1615f0f8ba032382c</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>Property:Hierarchy Data</title>
  <ns>102</ns>
  <id>47</id>
  <revision>
    <id>71</id>
    <timestamp>2015-12-26T23:28:30Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Code]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Code]].</text>
    <sha1>6f45f32988880c7b04366a0b6d289e6358daddd8</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>Property:Related to</title>
  <ns>102</ns>
  <id>48</id>
  <revision>
    <id>72</id>
    <timestamp>2015-12-26T23:29:32Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Page]].</text>
    <sha1>a77920a9d24db1d24320cdd74718a3bf351bd0c9</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>Property:Full Title</title>
  <ns>102</ns>
  <id>49</id>
  <revision>
    <id>73</id>
    <timestamp>2015-12-26T23:31:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>File:Reachback Support Operations.png</title>
  <ns>6</ns>
  <id>51</id>
  <revision>
    <id>78</id>
    <timestamp>2015-12-27T00:42:03Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>File:Target-icon.png</title>
  <ns>6</ns>
  <id>52</id>
  <revision>
    <id>80</id>
    <timestamp>2015-12-27T00:48:06Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>81</id>
    <parentid>80</parentid>
    <timestamp>2015-12-27T00:49:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[File:Target-1.png]] to [[File:Target-icon.png]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>Cell system</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>83</id>
    <parentid>4</parentid>
    <timestamp>2015-12-27T01:20:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39438" xml:space="preserve">{{for|the general use of a cellular structure by an organization, such as by a business|Cellular organization (disambiguation)}}
{{redirect|Sleeper cell}}
{{Use dmy dates|date=July 2011}}
{{multiple issues|
{{Essay-like|date=July 2011}}
{{POV|date=September 2012}}
{{Original research|date=January 2015}}
{{cleanup|reason=Poorly written, poorly referenced, marked essay-like (mostly user Hcberkowitz's edits; see page history) and POV issues and generally underlinked|date=January 2015}}
{{cleanup-rewrite|date=January 2015}}
{{Expert-subject|date=January 2015}}
}}

{{terrorism}}
A '''clandestine cell''' structure is a method for organizing a group of people like [[French resistance|resistance]] fighters or terrorists in such a way that it can more effectively resist penetration by an opposing organization (e.g., a law enforcement organization). In a cell structure, each small group of people in the cell only know the identities of the people in their cell; as such, if a cell member is apprehended and interrogated, he or she will not know the identities of the higher-ranking individuals in the organization. Depending on the group's [[philosophy]], its operational area, the communications technologies available, and the nature of the mission, it can range from a strict hierarchy to an extremely distributed organization. It is also a method used by [[organized crime|criminal organizations]], [[undercover]] operatives, and unconventional warfare (UW) units led by [[special forces]]. Historically, clandestine organizations have avoided electronic communications, because [[signals intelligence]] is a strength of conventional militaries and counterintelligence organizations.{{citation needed|date=August 2012}}

In the context of [[tradecraft]], [[covert operation|covert]] and [[clandestine operation|clandestine]] are not synonymous. As noted in the definition (which has been used by the United States and NATO since World War II) in a covert operation the identity of the sponsor is concealed, while in a clandestine operation the operation itself is concealed. Put differently, clandestine means "hidden", while covert means "deniable". The adversary is aware that a covert activity is happening, but does not know who is doing it, and certainly not their sponsorship. Clandestine activities, however, if successful, are completely unknown to the adversary, and their function, such as espionage, would be neutralized if there was any awareness of the activity.

A '''sleeper cell''' refers to a cell, or isolated grouping of [[sleeper agent]]s that lies dormant until it receives orders or decides to act.

==History==

=== Provisional Irish Republican Army===
As opposed to the [[French Resistance]], the modern [[Provisional Irish Republican Army]] (PIRA) has a history going back to Irish revolutionary forces in the early 20th century, but has little external control.  Its doctrine and organization have changed over time, given factors such as the independence of 26 of Ireland's 32 counties, the continued British control of Northern Ireland and the simple passage of time and changes in contemporary thinking and technology.&lt;ref name=Leahy&gt;{{cite web
 | url = http://cgsc.cdmhost.com/cgi-bin/showfile.exe?CISOROOT=/p4013coll2&amp;CISOPTR=386&amp;filename=387.pdf
 |format=PDF| author = Leahy, Kevin C.
 | year = 2005
 | title = The Impact of Technology on the Command, Control, and Organizational Structure of Insurgent Groups
 | accessdate=2007-12-04
}}&lt;/ref&gt;

Officially, the PIRA is hierarchical, but, especially as British security forces became more effective, changed to a semiautonomous model for its operational and certain of its support cells (e.g., transportation, intelligence, cover and security).&lt;ref name=GreenBook&gt;{{cite web
 | url = https://web.archive.org/web/20110606012137/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html
 | author = Irish Republican Army
 | title = The Green Book
 | accessdate=2007-12-04
|archiveurl=https://web.archive.org/web/20070616132240/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html|archivedate=2007-06-16}}&lt;/ref&gt; Its leadership sees itself as guiding and consensus-building. The lowest-level cells, typically of 2-5 people, tend to be built by people with an existing personal relationship. British counterinsurgents could fairly easily understand the command structure, but not the workings of the operational cells.

The IRA has an extensive network of inactive or sleeper cells, so new ''ad hoc'' organizations may appear for any specific operation.

===World War II French Resistance===
In World War II, [[Operation Jedburgh]] teams parachuted into occupied France to lead unconventional warfare units.&lt;ref name=Hall&gt;{{cite book
 | author = Hall, Roger
 | title = You're Stepping on my Cloak and Dagger
 | publisher = Bantam Books
 | year =1964
}}&lt;/ref&gt;&lt;ref name=SOETO&gt;{{cite book
 | chapterurl = http://www.history.army.mil/books/wwii/70-42/70-423.htm
 | chapter = Chapter 3: Special Operations in the European Theater
 | publisher = [[United States Army Center of Military History]]
| url = http://www.history.army.mil/books/wwii/70-42/70-42c.htm
| title = U.S. Army Special Operations in World War II
| first = David W.
| last = Hogan
| id = CMH Pub 70-42
|year = 1992
| location = Washington, D.C.
}}&lt;/ref&gt; They would be composed of two officers, one American or British, and the other French, the latter preferably from the area into which they landed. The third member of the team was a radio operator.

Especially through the French member, they would contact trusted individuals in the area of operation, and ask them to recruit a team of trusted subordinates (i.e., a subcell). If the team mission were sabotage, reconnaissance, or espionage, there was no need to meet in large units. If the team was to carry out direct action, often an unwise mission unless an appreciable number of the locals had military experience, it would be necessary to assemble into units for combat. Even then, the hideouts of the leadership were known only to subcell leaders. The legitimacy of the Jedburgh team came from its known affiliation with Allied powers, and it was a structure more appropriate for UW than for truly clandestine operations.

===National Front for the Liberation of South Vietnam===
Also known as the [[Viet Cong]], this organization grew from earlier anticolonial groups fighting the French, as well as anti-Japanese guerillas during World War II.&lt;ref name=VietCong&gt;{{cite book
 | author = Pike, Douglas
 | title = Viet Cong: Organization and Technique of the National Liberation Front of South Vietnam
 | publisher = MIT Press
 | year = 1970
}}&lt;/ref&gt;
Its command, control, and communication techniques derived from the experiences of these earlier insurgent groups. The group had extensive support from North Vietnam, and, indirectly, from the Soviet Union. It had parallel political and military structures, often overlapping. See [[Viet Cong and PAVN strategy and tactics]].
[[Image:Vcnvastructure4rev.jpg|thumb|right |A dual, but sometimes overlapping, Party and Military structure was top-down]]
The lowest level consisted of three-person cells who operated quite closely, and engaging in the sort of [[self-criticism]] common, as a bonding method, to Communist organizations.{{Citation needed|date=June 2014}}

==Parallel organizations==
The NLF and PIRA, as well as other movements, have chosen to have parallel political and military organizations. In the case of the NLF, other than some individuals with sanctuary in North Vietnam, the political organization could not be overt during the [[Vietnam War]]. After the war ended, surviving NLF officials held high office.

In the case of the PIRA, its political wing, [[Sinn Féin]], became increasingly overt, and then a full participant in politics. [[Hamas]] and [[Hezbollah]] also have variants of overt political/social service and covert military wings.

The overt political/social–covert military split avoided the inflexibility of a completely secret organization. Once an active insurgency began, the secrecy {{clarify span|could limit|date=January 2015}}&lt;!-- what? --&gt; freedom of action, distort information about goals and ideals, and restrict communication within the insurgency.&lt;ref name=FM3-24&gt;{{cite web
 | title = FM 3-24: Counterinsurgency
 | author = US Department of the Army
 |date=December 2006
 | url = https://fas.org/irp/doddir/army/fm3-24.pdf
|format=PDF}}&lt;/ref&gt; In a split organization, the public issues can be addressed overtly, while military actions were kept covert and intelligence functions stay clandestine.

==External support==
Many cell systems still receive, with due attention to security, support from the outside. This can range from leaders, trainers and supplies (such as the Jedburgh assistance to the French Resistance), or a safe haven for overt activities (such as the NLF spokesmen in Hanoi).

External support need not be overt. Certain Shi'a groups in Iraq, for example, do receive assistance from Iran{{Citation needed|date=March 2009}}, but this is not a public position of the government of Iran, and may even be limited to factions of that government.  Early US support to the Afghan Northern Alliance against the Taliban used clandestine operators from both the [[CIA]] and [[United States Army Special Forces]]. As the latter conflict escalated, the US participation became overt.

Note that both [[unconventional warfare]] (UW) (guerrilla operations) and [[foreign internal defense]] (FID) (counterinsurgency) may be covert and use cellular organization.

In a covert FID mission, only selected host nation (HN) leaders are aware of the foreign support organization. Under [[Operation White Star]], US personnel gave covert FID assistance to the Royal Lao Army starting in 1959, became overt in 1961, and ceased operations in 1962.

==Models of insurgency and associated cell characteristics==
While different kinds of insurgency differ in where they place clandestine or covert cells, when certain types of insurgency grow in power, the cell system is deemphasized. Cells still may be used for leadership security, but, if overt violence by organized units becomes significant, cells are less important. In Mao's three-stage doctrine,&lt;ref name=Mao1967&gt;{{cite book
 | title = On Protracted War
 | author = Mao,  Zedong | authorlink = Mao Zedong
 | year = 1967
 | publisher = Foreign Language Press, Beijing
}}&lt;/ref&gt; cells are still useful in Phase II to give cover to part-time guerillas, but, as the insurgency creates full-time military units in Phase III, the main units are the focus, not the cells. The [[Eighth Route Army]] did not run on a cell model.

When considering where cells exist with respect to the existing government, the type of insurgency needs to be considered. One US Army reference was Field Manual 100-20, which has been superseded by FM3-07.&lt;ref name=FM3-07&gt;{{cite web
 | title = FM 3-07 (formerly FM 100-20): Stability Operations and Support Operations
 | date = 20 February 2003
 | author = US Department of the Army
 | url = https://atiam.train.army.mil/soldierPortal/atia/adlsc/view/altfmt/9630-1
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; Drawing on this work, Nyberg (a [[United States Marine Corps]] officer) extended the ideas to describe four types of cell system, although his descriptions also encompass types of insurgencies that the cell system supports.&lt;ref name=Nyberg&gt;{{Cite journal
 | title = Insurgency: The Unsolved Mystery
 | first = Eric N. | last = Nyberg
 | publisher = US Marine Corps University Command and Staff College
 | year = 1991
 | url = http://www.globalsecurity.org/military/library/report/1991/NEN.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt;  At present, there is a new type associated with transnational terrorist insurgencies.

# Traditional: the slowest to form, this reflects a principally indigenous insurgency, initially with limited goals. It is more secure than others, as it tends to grow from people with social, cultural or family ties. The insurgents resent a government that has failed to recognize  tribal, racial, religious or linguistic groups "who perceive that the government has denied their rights and interests and work to establish or restore them. They seldom seek to overthrow the government or control the whole society; however, they frequently attempt to withdraw from government control through autonomy or semiautonomy." The Mujahideen in Afghanistan and the Kurdish revolt in Iraq illustrate the traditional pattern of insurgency. [[al-Qaeda]] generally operates in this mode, but if they become strong enough in a given area, they may change to the mass-oriented form.
# Subversive: Usually driven by an organization that contains at least some of the governing elite, some being sympathizers already in place, and others who penetrate the government. When they use violence, it has a specific purpose, such as coercing voters, intimidating officials, and disrupting and discrediting the government. Typically, there is a political arm (such as  [[Sinn Féin]] or the [[Viet Cong|National Liberation Front]]) that directs the military in planning carefully coordinated violence. "Employment of violence is designed to show the system to be incompetent and to provoke the government to an excessively violent response which further undermines its legitimacy." The [[Nazi]] rise to power, in the 1930s, is another example of subversion. Nazi members of parliament and street fighters were hardly clandestine, but the overall plan of the Nazi leadership to gain control of the nation was hidden. "A subversive insurgency is suited to a more permissive political environment which allows the insurgents to use both legal and illegal methods to accomplish their goals. Effective government resistance may convert this to a critical-cell model.
# Critical-cell: Critical cell is useful when the political climate becomes less permissive than one that allowed shadow cells. While other cell types try to form intelligence cells within the government, this type sets up "[[Continuity of government|shadow government]]" cells that can seize power once the system is destroyed both by external means and the internal subversion. This model fits the classic [[coup d'etat]],&lt;ref name=Luttwak&gt;{{cite book
 | title = Coup d'etat: A Practical Handbook
 | year = 1968
 | author = Luttwak, Edward | authorlink = Edward Luttwak
 | publisher = Harvard University Press
}}&lt;/ref&gt; and often tries to minimize violence. Variants include the [[Sandinista]] takeover of an existing government weakened by external popular revolution. "Insurgents also seek to infiltrate the government's institutions, but their object is to destroy the system from within." Clandestine cells form inside the government. "The use of violence remains covert until the government is so weakened that the insurgency's superior organization seizes power, supported by the armed force. One variation of this pattern is when the insurgent leadership permits the popular revolution to destroy the existing government, then emerges to direct the formation of a new government. Another variation is seen in the [[Cuba]]n revolution&lt;ref name=Guevara&gt;{{cite book
 | author = Guevara, Ernesto "Che"
 | title = On Guerilla Warfare
 | publisher = Praeger
 | year = 1961
}}&lt;/ref&gt; and is referred to as the foco (or Cuban model) insurgency. This model involves a single, armed cell which emerges in the midst of degenerating government legitimacy and becomes the nucleus around which mass popular support rallies.  The insurgents use this support to establish control and erect new institutions."
# Mass-oriented: where the subversive and covert-cell systems work from within the government, the mass-oriented builds a government completely outside the existing one, with the intention of replacing it. Such "insurgents patiently construct a base of passive and active political supporters, while simultaneously building a large armed element of guerrilla and regular forces.  They plan a protracted campaign of increasing violence to destroy the government and its institutions from the outside.  They have a well-developed ideology and carefully determine their objectives.  They are highly organized and effectively use propaganda and guerrilla action to mobilize forces for a direct political and military challenge to the government." The revolution that produced the [[Peoples' Republic of China]], the [[American Revolution]], and the [[Shining Path]] insurgency in Peru are examples of the mass-oriented model. Once established, this type of insurgency is extremely difficult to defeat because of its great depth of organization.

==Classic models for cell system operations==
Different kinds of cell organizations have been used for different purposes. This section focuses on clandestine cells, as would be used for [[espionage]], [[sabotage]], or the organization for [[unconventional warfare]]. When unconventional warfare starts using overt units, the cell system tends to be used only for sensitive leadership and intelligence roles.&lt;ref name=Mao1967 /&gt; The examples here will use [[CIA cryptonym]]s as a naming convention used to identify members of the cell system. Cryptonyms begin with a two-letter country or subject name (e.g., AL), followed with an arbitrary word. It is considered elegant to have the code merge with the other letters to form a pronounceable word.

===Operations under official cover===
Station BERRY operates, for country B, in target country BE. It has three case officers and several support officers. Espionage operation run by case officers under diplomatic cover, they would have to with the basic recruiting methods described in this article. Case officer BETTY runs the local agents BEN and BEATLE. Case officer BESSIE runs BENSON and BEAGLE.
[[Image:Wdip-Cell-0.png|thumb|Representative diplomatic-cover station and networks]]

Some recruits, due to the sensitivity of their position or their personalities not being appropriate for cell leadership, might not enter cells but be run as singletons, perhaps by other than the recruiting case officer. Asset BARD is a different sort of highly sensitive singleton, who is a joint asset of the country B, and the country identified by prefix AR. ARNOLD is a case officer from the country AR embassy, who knows only the case officer BERTRAM and the security officer BEST. ARNOLD does not know the station chief of BERRY or any of its other personnel. Other than BELL and BEST, the Station personnel only know BERTRAM as someone authorized to be in the Station, and who is known for his piano playing at embassy parties. He is covered as Cultural Attache, in a country that has very few pianos. Only the personnel involved with BARD know that ARNOLD is other than another friendly diplomat.

In contrast, BESSIE and BETTY know one another, and procedures exist for their taking over each other's assets in the event one of the two is disabled.

Some recruits, however, would be qualified to recruit their own subcell, as BEATLE has done. BESSIE knows the identity of BEATLE-1 and BEATLE-2, since he had them checked by headquarters counterintelligence before they were recruited. Note that a cryptonym does not imply anything about its  designee, such as gender.

===Clandestine presence===
The diagram of "initial team presence" shows that two teams, ALAN and ALICE, have successfully entered an area of operation, the country coded AL, but are only aware of a pool of potential recruits, and have not yet actually recruited anyone. They communicate with one another only through headquarters, so compromise of one team will not affect the other.
[[Image:Wnoc-Cell-0.png|thumb|left |Initial team presence by 2 separate clandestine teams with no official cover]]

Assume that in team ALAN, ALASTAIR is one of the officers with local contacts, might recruit two cell leaders, ALPINE and ALTITUDE. The other local officer in the team, ALBERT, recruits ALLOVER.  When ALPINE recruited two subcell members, they would be referred to as ALPINE-1 and ALPINE-2.

ALPINE and ALTITUDE only know how to reach ALASTAIR, but they are aware of at least some of other team members' identity should ALASTAIR be unavailable, and they would accept a message from ALBERT. Most often, the identity (and location) of the radio operator may not be shared. ALPINE and ALTITUDE, however, do not know one another. They do not know any of the members of team ALICE.

The legitimacy of the subcell structure came from the recruitment process, originally by the case officer and then by the cell leaders. Sometimes, the cell leader would propose subcell member names to the case officer, so the case officer could have a headquarters name check run before bringing the individual into the subcell. In principle, however, the subcell members would know ALPINE, and sometimes the other members of the ALPINE cell if they needed to work together; if ALPINE-1 and ALPINE-2 had independent assignments, they might not know each other. ALPINE-1 and ALPINE-2 certainly would not know ALASTAIR or anyone in the ALTITUDE or ALLOVER cells.
[[Image:Wnoc-Cell-1.png|thumb|Clandestine teams have built initial subcells]]

As the networks grow, a subcell leader might create his own cell, so ALPINE-2 might become the leader of the ALIMONY cell.

===Fault-tolerant cellular structures===
Modern communications theory has introduced methods to increase fault tolerance in cell organizations. In the past, if cell members only knew the cell leader, and the leader was neutralized, the cell was cut off from the rest of the organization. Game theory and graph theory have been applied to the study of optimal covert network design (see Lindelauf, R.H.A. et al. 2009. The influence of secrecy on the communication structure of covert networks. Social Networks 31: 126-137).

If a traditional cell had independent communications with the foreign support organization, headquarters might be able to arrange its reconnection. Another method is to have impersonal communications "side links" between cells, such as a pair of [[dead drop]]s, one for Team ALAN to leave "lost contact" messages to be retrieved by Team ALICE, and another dead drop for Team ALICE to leave messages for Team ALAN.

These links, to be used only on losing contact, do not guarantee a contact. When a team finds a message in its emergency drop, it might do no more than send an alert message to headquarters. Headquarters might determine, through [[SIGINT]] or other sources, that the enemy had captured the leadership and the entire team, and order the other team not to attempt contact. If headquarters can have reasonable confidence that there is a communications failure or partial compromise, it might send a new contact to the survivors.

When the cut-off team has electronic communications, such as the Internet, it has a much better chance of eluding surveillance and getting emergency instructions than by using a dead drop that can be under physical surveillance.

==Non-traditional models, exemplified by al-Qaeda==
Due to cultural differences, assuming the ''al-Qaeda Training Manual''&lt;ref name=AQTM&gt;{{cite web
 | url = https://fas.org/irp/world/para/aqmanual.pdf
 |format=PDF| title = al-Qaeda training manual
 | publisher = US Southern District Court, US New York City Attorney's Office, entered as evidence in Africa embassy bombings
}}&lt;/ref&gt; is authentic, eastern cell structures may differ from the Western mode. "Al-Qaida's minimal core group, only accounting for the leadership, can also be viewed topologically as a ring or chain network, with each leader/node heading their own particular hierarchy.

"Such networks function by having their sub-networks provide information and other forms of support (the ‘many-to-one’ model), while the core group supplies ‘truth’ and decisions/directions (the ‘one-to-many’ model). Trust and personal relationships are an essential part of the Al-Qaida network (a limiting factor, even while it provides enhanced security). Even while cell members are trained as ‘replaceable’ units, ‘vetting’ of members occurs during the invited training period under the observation of the core group.&lt;ref name=Sleepers&gt;{{cite web
 | url = http://www.metatempo.com/huntingthesleepers.pdf
 |format=PDF| title = Hunting the Sleepers: Tracking al-Qaida's Covert Operatives
 | date = 2001-12-31
 | author = Decision Support Systems, Inc.
 | accessdate = 2007-11-17
}}&lt;/ref&gt;

Cells of this structure are built outwards, from an internal leadership core. Superficially, this might be likened to a Western cell structure that emanates from a headquarters, but the Western centrality is bureaucratic, while structures in other non-western cultures builds on close personal relationships, often built over years, perhaps involving family or other in-group linkages. Such in-groups are thus extremely hard to infiltrate; infiltration has a serious chance only outside the in-group. Still, it may be possible for an in-group to be compromised through [[COMINT]] or, in rare cases, by compromising a member.

The core group is logically a ring, but is superimposed on an inner hub-and-spoke structure of ideological authority. Each member of the core forms another hub and spoke system (see [[#Infrastructure cells|infrastructure cells]]), the spokes leading to infrastructure cells under the supervision of the core group member, and possibly to operational groups which the headquarters support. Note that in this organization, there is a point at which the operational cell becomes autonomous of the core. Members surviving the operation may rejoin at various points.
[[Image:T-Cell-0.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

Osama, in this model, has the main responsibility of commanding the organization and being the spokesman on propaganda video and audio messages distributed by the propaganda cell. The other members of the core each command one or more infrastructure cells.

While the tight coupling enhances security, it can limit flexibility and the ability to scale the organization. This in-group, while sharing tight cultural and ideological values, is not committed to a bureaucratic process.

"Members of the core group are under what could be termed 'positive control'—long relationships
and similar mindsets make 'control' not so much of an issue, but there are distinct roles, and position (structural, financial, spiritual) determines authority, thus making the core group a hierarchy topologically.&lt;ref name=Sleepers /&gt;

In the first example of the core, each member knows how to reach two other members, and also knows the member(s) he considers his ideological superior. Solid lines show basic communication, dotted red arrows show the first level of ideological respect, and dotted blue arrows show a second level of ideological respect.

If Osama, the most respected, died, the core would reconstitute itself. While different members have an individual ideological guide, and these are not the same for all members, the core would reconstitute itself with Richard as most respected.

Assume there are no losses, and Osama can be reached directly only by members of the core group. Members of outer cells and support systems might know him only as "the Commander", or, as in the actual case of al-Qaeda, Osama bin Laden's face is recognizable worldwide, but only a few people know where he was or even how to contact him.

===Infrastructure cells===
Any clandestine or covert service, especially a non-national one, needs a variety of technical and administrative functions. Some of these services include:&lt;ref name=Sleepers /&gt;

# Forged documents and counterfeit currency
# Apartments and hiding places
# Communication means
# Transportation means
# Information
# Arms and ammunition
# Transport

Other functions include psychological operations, training, and finance.

A national intelligence service&lt;ref name=CIAsupport&gt;{{cite web
 | url = https://www.cia.gov/offices-of-cia/mission-support/who-we-are.html
 | author = US Central Intelligence Agency
 | title = Support to Mission: Who We Are
 | accessdate = 2007-11-19
}}&lt;/ref&gt;
has a support organization to deal with services such as finance, logistics, facilities (e.g., [[#Safehouses and Other Meeting Places|safehouses]]), information technology, communications, training, weapons and explosives, medical services, etc. Transportation alone is a huge function, including the need to buy tickets without drawing suspicion, and, where appropriate, using private vehicles. Finance includes the need to transfer money without coming under the suspicion of financial security organizations.

Some of these functions, such as finance, are far harder to operate in remote areas, such as the [[FATA]] of [[Pakistan]], than in cities with large numbers of official and unofficial financial institutions, and the communications to support them. If the financial office is distant from the remote headquarters, there is a need for [[couriers]], who must be trusted to some extent, but they may not know the contents of their messages or the actual identity of sender and/or receiver. The couriers, depending on the balance among type and size of message, security, and technology available, may memorize messages, carry audio or video recordings, or hand-carry computer media.
[[Image:T-Cell-1.png|thumb|Core group and infrastructure cells; military cells in training]]

"These cells are socially embedded (less so than the core group, however), structurally embedded, functionally embedded (they are specialized into a domain), and knowledge base-specific (there does not seem to be a great deal of cross-training, or lateral mobility in the organization). Such cells are probably subjected to a mixture of positive and negative control ("do this, do these sorts of things, don’t do that")."&lt;ref name=Sleepers /&gt;

{| class="wikitable"
&lt;caption&gt;Core Structure of Non-National Group&lt;/caption&gt;
|-
! Member
! Infrastructure commanded
|-
| Richard
| Finance
|-
| Anton
| Military training/operations 1
|-
| Hassan
| Military training/operations 2
|-
| David
| Transportation
|-
| Kim
| Communications and propaganda
|}

The leaders of military cells are responsible for training them, and, when an operation is scheduled, selecting the operational commander, giving him the basic objective and arranging whatever support is needed, and then release him from tight control to execute the meeting. Depending on the specific case, the military leaders might have direct, possibly one-way, communications with their cells, or they might have to give Kim the messages to be transmitted, by means that Anton and Hassan have no need to know.

Note that Anton does not have a direct connection to Kim. Under normal circumstances, he sacrifices efficiency for security, by passing communications requests through Hassan. The security structure also means that Hassan does not know the members of Anton's cells, and Kim may know only ways to communicate with them but not their identity.

Kim operates two systems of cells, one for secure communications and one for propaganda. To send out a propaganda message, Osama must pass it to Kim. If Kim were compromised, the core group might have significant problems with any sort of outside communications.

Terrorist networks do not match cleanly to other cell systems that regularly report to a headquarters. The apparent al-Qaeda methodology of letting operational cells decide on their final dates and means of attack exhibit an operational pattern, but not a periodicity that could easily be used for an [[Intelligence analysis management#Indications &amp; warning checklists|indications checklist]] appropriate for a warning center. Such lists depend on seeing a local pattern to give a specific warning.&lt;ref name=Vos&gt;{{cite web
 | title = Modeling Terrorist Networks - Complex Systems at the Mid-Range
 | first1 = Philip Vos
 | last1 = Fellman
 | first2 = Roxana
 | last2 = Wright
 | url = http://www.psych.lse.ac.uk/complexity/Conference/FellmanWright.pdf
 |format=PDF| accessdate = 2007-11-02
}}&lt;/ref&gt;

Note that Hassan has two subordinates that have not yet established operational cells. These subordinates can be considered '''sleepers''', but not necessarily with a sleeper cell.

===Operational cells===
For each mission are created one or more operational cells. If the al-Qaeda signature of multiple concurrent attacks is used, there may be an operational cell for each target location. It will depend on the operation if they will need any support cells in the operational area. For example, it may be more secure to have a local cell build bombs, which will be delivered by cells coming from outside the area.

"Operational cells are not created, but instead 'seeded' utilizing individuals spotted or that request assistance (both groups are 'vetted' by being trained under the observation of the core group, which dramatically restricts the opportunity for passing off walk-ins under false flag). Categorization of operational cells appears to be by capabilities, region, and then task/operation. Operational cells are composed of members whose worldview has been firmly tested—necessary to front-load, because such cells are dispersed back to their own local control (or negative control—proscribed behavior—with positive control only coming in the form of contact for synchronization or support)."&lt;ref name=Sleepers /&gt;

If operational cells routinely are "released" ''curved dotted lines on link to military cells'' to select their final operational parameters, they use a different paradigm than governmental clandestine or covert operations. On a number of cases, US special operations forces had to wait for Presidential authorization to make an attack, or even move to staging areas. Admittedly, a country would have to face the consequences of an inappropriate attack, so it may tend to be overcautious, where a terror network would merely shrug at the world being upset. Assuming that the al-Qaeda operational technique is not to use positive control, their operations may be more random, but also more unpredictable for counterterror forces. If their cells truly need constant control, there are communications links that might be detected by SIGINT, and if their command can be disrupted, the field units could not function. Since there is fairly little downside for terrorists to attack out of synchronization with other activities, the lack of positive control becomes a strength of their approach to cell organization.
[[Image:T-Cell-2.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

The operational cells need to have continuous internal communication; there is a commander, who may be in touch with infrastructure cells or, less likely from a security standpoint with the core group.

Al-Qaeda's approach, which even differs from that of earlier terrorist organizations, may be very viable for their goals:

* Cells are redundant and distributed, making them difficult to ‘roll up’
* Cells are coordinated, not under "command &amp; control"—this autonomy and local control makes them flexible, and enhances security
* Trust and comcon internally to the cell provide redundancy of potential command (a failure of Palestinian operations in the past), and well as a shared knowledgebase (which may mean, over time, that ‘cross training’ emerges inside a cell, providing redundancy of most critical skills and knowledge).&lt;ref name=Sleepers /&gt;

===Indirect support networks===
In the above graphic, note the indirect support network controlled by Richard's subcell.

"While Al-Qaida has elements of the organization designed to support the structure, but such elements are insufficient in meeting the needs of such an organization, and for security reasons there would be redundant and secondary-/tertiary-networks that are unaware of their connection to Al-Qaida. These networks, primarily related to fundraising and financial activities, as well as technology providers, are in a ‘use’ relationship with Al-Qaida—managed through cut-outs or individuals that do not inform them of the nature of activities, and that may have a cover pretext sufficient to deflect questions or inquiry."&lt;ref name=Sleepers /&gt;

===A possible countermeasure===
In 2002, ''U.S. News &amp; World Report'' said that American intelligence is beginning to acquire a sufficiently critical mass of intelligence on al-Qaida indicating, "Once thought nearly impossible to penetrate, al Qaeda is proving no tougher a target than the KGB or the Mafia--closed societies that took the U.S. government years to get inside. "We're getting names, the different camps they trained at, the hierarchy, the infighting," says an intelligence official. "It's very promising."&lt;ref name=Kaplan2002&gt;{{Cite journal
 | title = Run and Gun: Al Qaeda arrests and intelligence hauls bring new energy to the war on terrorism
 | first = David E. | last = Kaplan
 | date = 22 September 2002
 | journal = U.S. News &amp; World Report
 | url = http://www.usnews.com/usnews/news/articles/020930/archive_022824.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; The report also said that the collected data has allowed the recruiting of informants.

Writing in the U.S. Army journal ''Military Review'', David W. Pendall  suggested that a "catch-and-release program for suspected operatives might create reluctance or distrust in such suspects and prevent them from further acts or, perhaps more important, create distrust in the cell leaders of these individuals in the future." The author noted the press release describing Ramzi Binalshib's cooperation with the United States "are sure to prevent reentry into a terrorist cell as a trusted member and most likely limits the further trust and assignments of close cell associates still at large. The captor would determine when to name names and when to remain silent."&lt;ref name=Pendall2004&gt;{{Cite journal
 | date = January–February 2004
 | journal = Military Review
 | url = http://calldp.leavenworth.army.mil
 | first = David W. | last = Pendall
 | title =Effects-Based Operations and the Exercise of National Power
 | publisher = [[United States Army Combined Arms Center]]
 | postscript = &lt;!--None--&gt;
}}  Find the article by going through the Military Review directories&lt;/ref&gt; Indeed, once intelligence learns the name and characteristics of an at-large adversary, as well as some sensitive information that would plausibly be known to him, a news release could be issued to talk about his cooperation. Such a method could not be used too often, but, used carefully, could disturb the critical trust networks. The greatest uncertainty might be associated with throwing doubt onto a key member of an operational cell that has gone autonomous.

==See also==
* [[Leaderless resistance]]
* [[Lone wolf (terrorism)]]

==References==
{{reflist | 2}}

==External links==
* [http://theriskyshift.com/2012/06/an-introduction-to-terrorist-organisational-structures/ An Introduction To Terrorist Organisational Structures]

{{Intelligence cycle management}}

[[Category:Counter-intelligence]]
[[Category:Types of espionage]]
[[Category:Intelligence analysis]]
[[Category:Military intelligence]]
[[Category:Military tactics]]
[[Category:Secrecy]]
[[Category:Terrorism tactics]]

[http://www.cimacell.com/wiki| Structure]</text>
    <sha1>21fb2abfb61af519af0475aba332a66b543ed9ba</sha1>
  </revision>
  <revision>
    <id>84</id>
    <parentid>83</parentid>
    <timestamp>2015-12-27T01:22:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39437" xml:space="preserve">{{for|the general use of a cellular structure by an organization, such as by a business|Cellular organization (disambiguation)}}
{{redirect|Sleeper cell}}
{{Use dmy dates|date=July 2011}}
{{multiple issues|
{{Essay-like|date=July 2011}}
{{POV|date=September 2012}}
{{Original research|date=January 2015}}
{{cleanup|reason=Poorly written, poorly referenced, marked essay-like (mostly user Hcberkowitz's edits; see page history) and POV issues and generally underlinked|date=January 2015}}
{{cleanup-rewrite|date=January 2015}}
{{Expert-subject|date=January 2015}}
}}

{{terrorism}}
A '''clandestine cell''' structure is a method for organizing a group of people like [[French resistance|resistance]] fighters or terrorists in such a way that it can more effectively resist penetration by an opposing organization (e.g., a law enforcement organization). In a cell structure, each small group of people in the cell only know the identities of the people in their cell; as such, if a cell member is apprehended and interrogated, he or she will not know the identities of the higher-ranking individuals in the organization. Depending on the group's [[philosophy]], its operational area, the communications technologies available, and the nature of the mission, it can range from a strict hierarchy to an extremely distributed organization. It is also a method used by [[organized crime|criminal organizations]], [[undercover]] operatives, and unconventional warfare (UW) units led by [[special forces]]. Historically, clandestine organizations have avoided electronic communications, because [[signals intelligence]] is a strength of conventional militaries and counterintelligence organizations.{{citation needed|date=August 2012}}

In the context of [[tradecraft]], [[covert operation|covert]] and [[clandestine operation|clandestine]] are not synonymous. As noted in the definition (which has been used by the United States and NATO since World War II) in a covert operation the identity of the sponsor is concealed, while in a clandestine operation the operation itself is concealed. Put differently, clandestine means "hidden", while covert means "deniable". The adversary is aware that a covert activity is happening, but does not know who is doing it, and certainly not their sponsorship. Clandestine activities, however, if successful, are completely unknown to the adversary, and their function, such as espionage, would be neutralized if there was any awareness of the activity.

A '''sleeper cell''' refers to a cell, or isolated grouping of [[sleeper agent]]s that lies dormant until it receives orders or decides to act.

==History==

=== Provisional Irish Republican Army===
As opposed to the [[French Resistance]], the modern [[Provisional Irish Republican Army]] (PIRA) has a history going back to Irish revolutionary forces in the early 20th century, but has little external control.  Its doctrine and organization have changed over time, given factors such as the independence of 26 of Ireland's 32 counties, the continued British control of Northern Ireland and the simple passage of time and changes in contemporary thinking and technology.&lt;ref name=Leahy&gt;{{cite web
 | url = http://cgsc.cdmhost.com/cgi-bin/showfile.exe?CISOROOT=/p4013coll2&amp;CISOPTR=386&amp;filename=387.pdf
 |format=PDF| author = Leahy, Kevin C.
 | year = 2005
 | title = The Impact of Technology on the Command, Control, and Organizational Structure of Insurgent Groups
 | accessdate=2007-12-04
}}&lt;/ref&gt;

Officially, the PIRA is hierarchical, but, especially as British security forces became more effective, changed to a semiautonomous model for its operational and certain of its support cells (e.g., transportation, intelligence, cover and security).&lt;ref name=GreenBook&gt;{{cite web
 | url = https://web.archive.org/web/20110606012137/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html
 | author = Irish Republican Army
 | title = The Green Book
 | accessdate=2007-12-04
|archiveurl=https://web.archive.org/web/20070616132240/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html|archivedate=2007-06-16}}&lt;/ref&gt; Its leadership sees itself as guiding and consensus-building. The lowest-level cells, typically of 2-5 people, tend to be built by people with an existing personal relationship. British counterinsurgents could fairly easily understand the command structure, but not the workings of the operational cells.

The IRA has an extensive network of inactive or sleeper cells, so new ''ad hoc'' organizations may appear for any specific operation.

===World War II French Resistance===
In World War II, [[Operation Jedburgh]] teams parachuted into occupied France to lead unconventional warfare units.&lt;ref name=Hall&gt;{{cite book
 | author = Hall, Roger
 | title = You're Stepping on my Cloak and Dagger
 | publisher = Bantam Books
 | year =1964
}}&lt;/ref&gt;&lt;ref name=SOETO&gt;{{cite book
 | chapterurl = http://www.history.army.mil/books/wwii/70-42/70-423.htm
 | chapter = Chapter 3: Special Operations in the European Theater
 | publisher = [[United States Army Center of Military History]]
| url = http://www.history.army.mil/books/wwii/70-42/70-42c.htm
| title = U.S. Army Special Operations in World War II
| first = David W.
| last = Hogan
| id = CMH Pub 70-42
|year = 1992
| location = Washington, D.C.
}}&lt;/ref&gt; They would be composed of two officers, one American or British, and the other French, the latter preferably from the area into which they landed. The third member of the team was a radio operator.

Especially through the French member, they would contact trusted individuals in the area of operation, and ask them to recruit a team of trusted subordinates (i.e., a subcell). If the team mission were sabotage, reconnaissance, or espionage, there was no need to meet in large units. If the team was to carry out direct action, often an unwise mission unless an appreciable number of the locals had military experience, it would be necessary to assemble into units for combat. Even then, the hideouts of the leadership were known only to subcell leaders. The legitimacy of the Jedburgh team came from its known affiliation with Allied powers, and it was a structure more appropriate for UW than for truly clandestine operations.

===National Front for the Liberation of South Vietnam===
Also known as the [[Viet Cong]], this organization grew from earlier anticolonial groups fighting the French, as well as anti-Japanese guerillas during World War II.&lt;ref name=VietCong&gt;{{cite book
 | author = Pike, Douglas
 | title = Viet Cong: Organization and Technique of the National Liberation Front of South Vietnam
 | publisher = MIT Press
 | year = 1970
}}&lt;/ref&gt;
Its command, control, and communication techniques derived from the experiences of these earlier insurgent groups. The group had extensive support from North Vietnam, and, indirectly, from the Soviet Union. It had parallel political and military structures, often overlapping. See [[Viet Cong and PAVN strategy and tactics]].
[[Image:Vcnvastructure4rev.jpg|thumb|right |A dual, but sometimes overlapping, Party and Military structure was top-down]]
The lowest level consisted of three-person cells who operated quite closely, and engaging in the sort of [[self-criticism]] common, as a bonding method, to Communist organizations.{{Citation needed|date=June 2014}}

==Parallel organizations==
The NLF and PIRA, as well as other movements, have chosen to have parallel political and military organizations. In the case of the NLF, other than some individuals with sanctuary in North Vietnam, the political organization could not be overt during the [[Vietnam War]]. After the war ended, surviving NLF officials held high office.

In the case of the PIRA, its political wing, [[Sinn Féin]], became increasingly overt, and then a full participant in politics. [[Hamas]] and [[Hezbollah]] also have variants of overt political/social service and covert military wings.

The overt political/social–covert military split avoided the inflexibility of a completely secret organization. Once an active insurgency began, the secrecy {{clarify span|could limit|date=January 2015}}&lt;!-- what? --&gt; freedom of action, distort information about goals and ideals, and restrict communication within the insurgency.&lt;ref name=FM3-24&gt;{{cite web
 | title = FM 3-24: Counterinsurgency
 | author = US Department of the Army
 |date=December 2006
 | url = https://fas.org/irp/doddir/army/fm3-24.pdf
|format=PDF}}&lt;/ref&gt; In a split organization, the public issues can be addressed overtly, while military actions were kept covert and intelligence functions stay clandestine.

==External support==
Many cell systems still receive, with due attention to security, support from the outside. This can range from leaders, trainers and supplies (such as the Jedburgh assistance to the French Resistance), or a safe haven for overt activities (such as the NLF spokesmen in Hanoi).

External support need not be overt. Certain Shi'a groups in Iraq, for example, do receive assistance from Iran{{Citation needed|date=March 2009}}, but this is not a public position of the government of Iran, and may even be limited to factions of that government.  Early US support to the Afghan Northern Alliance against the Taliban used clandestine operators from both the [[CIA]] and [[United States Army Special Forces]]. As the latter conflict escalated, the US participation became overt.

Note that both [[unconventional warfare]] (UW) (guerrilla operations) and [[foreign internal defense]] (FID) (counterinsurgency) may be covert and use cellular organization.

In a covert FID mission, only selected host nation (HN) leaders are aware of the foreign support organization. Under [[Operation White Star]], US personnel gave covert FID assistance to the Royal Lao Army starting in 1959, became overt in 1961, and ceased operations in 1962.

==Models of insurgency and associated cell characteristics==
While different kinds of insurgency differ in where they place clandestine or covert cells, when certain types of insurgency grow in power, the cell system is deemphasized. Cells still may be used for leadership security, but, if overt violence by organized units becomes significant, cells are less important. In Mao's three-stage doctrine,&lt;ref name=Mao1967&gt;{{cite book
 | title = On Protracted War
 | author = Mao,  Zedong | authorlink = Mao Zedong
 | year = 1967
 | publisher = Foreign Language Press, Beijing
}}&lt;/ref&gt; cells are still useful in Phase II to give cover to part-time guerillas, but, as the insurgency creates full-time military units in Phase III, the main units are the focus, not the cells. The [[Eighth Route Army]] did not run on a cell model.

When considering where cells exist with respect to the existing government, the type of insurgency needs to be considered. One US Army reference was Field Manual 100-20, which has been superseded by FM3-07.&lt;ref name=FM3-07&gt;{{cite web
 | title = FM 3-07 (formerly FM 100-20): Stability Operations and Support Operations
 | date = 20 February 2003
 | author = US Department of the Army
 | url = https://atiam.train.army.mil/soldierPortal/atia/adlsc/view/altfmt/9630-1
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; Drawing on this work, Nyberg (a [[United States Marine Corps]] officer) extended the ideas to describe four types of cell system, although his descriptions also encompass types of insurgencies that the cell system supports.&lt;ref name=Nyberg&gt;{{Cite journal
 | title = Insurgency: The Unsolved Mystery
 | first = Eric N. | last = Nyberg
 | publisher = US Marine Corps University Command and Staff College
 | year = 1991
 | url = http://www.globalsecurity.org/military/library/report/1991/NEN.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt;  At present, there is a new type associated with transnational terrorist insurgencies.

# Traditional: the slowest to form, this reflects a principally indigenous insurgency, initially with limited goals. It is more secure than others, as it tends to grow from people with social, cultural or family ties. The insurgents resent a government that has failed to recognize  tribal, racial, religious or linguistic groups "who perceive that the government has denied their rights and interests and work to establish or restore them. They seldom seek to overthrow the government or control the whole society; however, they frequently attempt to withdraw from government control through autonomy or semiautonomy." The Mujahideen in Afghanistan and the Kurdish revolt in Iraq illustrate the traditional pattern of insurgency. [[al-Qaeda]] generally operates in this mode, but if they become strong enough in a given area, they may change to the mass-oriented form.
# Subversive: Usually driven by an organization that contains at least some of the governing elite, some being sympathizers already in place, and others who penetrate the government. When they use violence, it has a specific purpose, such as coercing voters, intimidating officials, and disrupting and discrediting the government. Typically, there is a political arm (such as  [[Sinn Féin]] or the [[Viet Cong|National Liberation Front]]) that directs the military in planning carefully coordinated violence. "Employment of violence is designed to show the system to be incompetent and to provoke the government to an excessively violent response which further undermines its legitimacy." The [[Nazi]] rise to power, in the 1930s, is another example of subversion. Nazi members of parliament and street fighters were hardly clandestine, but the overall plan of the Nazi leadership to gain control of the nation was hidden. "A subversive insurgency is suited to a more permissive political environment which allows the insurgents to use both legal and illegal methods to accomplish their goals. Effective government resistance may convert this to a critical-cell model.
# Critical-cell: Critical cell is useful when the political climate becomes less permissive than one that allowed shadow cells. While other cell types try to form intelligence cells within the government, this type sets up "[[Continuity of government|shadow government]]" cells that can seize power once the system is destroyed both by external means and the internal subversion. This model fits the classic [[coup d'etat]],&lt;ref name=Luttwak&gt;{{cite book
 | title = Coup d'etat: A Practical Handbook
 | year = 1968
 | author = Luttwak, Edward | authorlink = Edward Luttwak
 | publisher = Harvard University Press
}}&lt;/ref&gt; and often tries to minimize violence. Variants include the [[Sandinista]] takeover of an existing government weakened by external popular revolution. "Insurgents also seek to infiltrate the government's institutions, but their object is to destroy the system from within." Clandestine cells form inside the government. "The use of violence remains covert until the government is so weakened that the insurgency's superior organization seizes power, supported by the armed force. One variation of this pattern is when the insurgent leadership permits the popular revolution to destroy the existing government, then emerges to direct the formation of a new government. Another variation is seen in the [[Cuba]]n revolution&lt;ref name=Guevara&gt;{{cite book
 | author = Guevara, Ernesto "Che"
 | title = On Guerilla Warfare
 | publisher = Praeger
 | year = 1961
}}&lt;/ref&gt; and is referred to as the foco (or Cuban model) insurgency. This model involves a single, armed cell which emerges in the midst of degenerating government legitimacy and becomes the nucleus around which mass popular support rallies.  The insurgents use this support to establish control and erect new institutions."
# Mass-oriented: where the subversive and covert-cell systems work from within the government, the mass-oriented builds a government completely outside the existing one, with the intention of replacing it. Such "insurgents patiently construct a base of passive and active political supporters, while simultaneously building a large armed element of guerrilla and regular forces.  They plan a protracted campaign of increasing violence to destroy the government and its institutions from the outside.  They have a well-developed ideology and carefully determine their objectives.  They are highly organized and effectively use propaganda and guerrilla action to mobilize forces for a direct political and military challenge to the government." The revolution that produced the [[Peoples' Republic of China]], the [[American Revolution]], and the [[Shining Path]] insurgency in Peru are examples of the mass-oriented model. Once established, this type of insurgency is extremely difficult to defeat because of its great depth of organization.

==Classic models for cell system operations==
Different kinds of cell organizations have been used for different purposes. This section focuses on clandestine cells, as would be used for [[espionage]], [[sabotage]], or the organization for [[unconventional warfare]]. When unconventional warfare starts using overt units, the cell system tends to be used only for sensitive leadership and intelligence roles.&lt;ref name=Mao1967 /&gt; The examples here will use [[CIA cryptonym]]s as a naming convention used to identify members of the cell system. Cryptonyms begin with a two-letter country or subject name (e.g., AL), followed with an arbitrary word. It is considered elegant to have the code merge with the other letters to form a pronounceable word.

===Operations under official cover===
Station BERRY operates, for country B, in target country BE. It has three case officers and several support officers. Espionage operation run by case officers under diplomatic cover, they would have to with the basic recruiting methods described in this article. Case officer BETTY runs the local agents BEN and BEATLE. Case officer BESSIE runs BENSON and BEAGLE.
[[Image:Wdip-Cell-0.png|thumb|Representative diplomatic-cover station and networks]]

Some recruits, due to the sensitivity of their position or their personalities not being appropriate for cell leadership, might not enter cells but be run as singletons, perhaps by other than the recruiting case officer. Asset BARD is a different sort of highly sensitive singleton, who is a joint asset of the country B, and the country identified by prefix AR. ARNOLD is a case officer from the country AR embassy, who knows only the case officer BERTRAM and the security officer BEST. ARNOLD does not know the station chief of BERRY or any of its other personnel. Other than BELL and BEST, the Station personnel only know BERTRAM as someone authorized to be in the Station, and who is known for his piano playing at embassy parties. He is covered as Cultural Attache, in a country that has very few pianos. Only the personnel involved with BARD know that ARNOLD is other than another friendly diplomat.

In contrast, BESSIE and BETTY know one another, and procedures exist for their taking over each other's assets in the event one of the two is disabled.

Some recruits, however, would be qualified to recruit their own subcell, as BEATLE has done. BESSIE knows the identity of BEATLE-1 and BEATLE-2, since he had them checked by headquarters counterintelligence before they were recruited. Note that a cryptonym does not imply anything about its  designee, such as gender.

===Clandestine presence===
The diagram of "initial team presence" shows that two teams, ALAN and ALICE, have successfully entered an area of operation, the country coded AL, but are only aware of a pool of potential recruits, and have not yet actually recruited anyone. They communicate with one another only through headquarters, so compromise of one team will not affect the other.
[[Image:Wnoc-Cell-0.png|thumb|left |Initial team presence by 2 separate clandestine teams with no official cover]]

Assume that in team ALAN, ALASTAIR is one of the officers with local contacts, might recruit two cell leaders, ALPINE and ALTITUDE. The other local officer in the team, ALBERT, recruits ALLOVER.  When ALPINE recruited two subcell members, they would be referred to as ALPINE-1 and ALPINE-2.

ALPINE and ALTITUDE only know how to reach ALASTAIR, but they are aware of at least some of other team members' identity should ALASTAIR be unavailable, and they would accept a message from ALBERT. Most often, the identity (and location) of the radio operator may not be shared. ALPINE and ALTITUDE, however, do not know one another. They do not know any of the members of team ALICE.

The legitimacy of the subcell structure came from the recruitment process, originally by the case officer and then by the cell leaders. Sometimes, the cell leader would propose subcell member names to the case officer, so the case officer could have a headquarters name check run before bringing the individual into the subcell. In principle, however, the subcell members would know ALPINE, and sometimes the other members of the ALPINE cell if they needed to work together; if ALPINE-1 and ALPINE-2 had independent assignments, they might not know each other. ALPINE-1 and ALPINE-2 certainly would not know ALASTAIR or anyone in the ALTITUDE or ALLOVER cells.
[[Image:Wnoc-Cell-1.png|thumb|Clandestine teams have built initial subcells]]

As the networks grow, a subcell leader might create his own cell, so ALPINE-2 might become the leader of the ALIMONY cell.

===Fault-tolerant cellular structures===
Modern communications theory has introduced methods to increase fault tolerance in cell organizations. In the past, if cell members only knew the cell leader, and the leader was neutralized, the cell was cut off from the rest of the organization. Game theory and graph theory have been applied to the study of optimal covert network design (see Lindelauf, R.H.A. et al. 2009. The influence of secrecy on the communication structure of covert networks. Social Networks 31: 126-137).

If a traditional cell had independent communications with the foreign support organization, headquarters might be able to arrange its reconnection. Another method is to have impersonal communications "side links" between cells, such as a pair of [[dead drop]]s, one for Team ALAN to leave "lost contact" messages to be retrieved by Team ALICE, and another dead drop for Team ALICE to leave messages for Team ALAN.

These links, to be used only on losing contact, do not guarantee a contact. When a team finds a message in its emergency drop, it might do no more than send an alert message to headquarters. Headquarters might determine, through [[SIGINT]] or other sources, that the enemy had captured the leadership and the entire team, and order the other team not to attempt contact. If headquarters can have reasonable confidence that there is a communications failure or partial compromise, it might send a new contact to the survivors.

When the cut-off team has electronic communications, such as the Internet, it has a much better chance of eluding surveillance and getting emergency instructions than by using a dead drop that can be under physical surveillance.

==Non-traditional models, exemplified by al-Qaeda==
Due to cultural differences, assuming the ''al-Qaeda Training Manual''&lt;ref name=AQTM&gt;{{cite web
 | url = https://fas.org/irp/world/para/aqmanual.pdf
 |format=PDF| title = al-Qaeda training manual
 | publisher = US Southern District Court, US New York City Attorney's Office, entered as evidence in Africa embassy bombings
}}&lt;/ref&gt; is authentic, eastern cell structures may differ from the Western mode. "Al-Qaida's minimal core group, only accounting for the leadership, can also be viewed topologically as a ring or chain network, with each leader/node heading their own particular hierarchy.

"Such networks function by having their sub-networks provide information and other forms of support (the ‘many-to-one’ model), while the core group supplies ‘truth’ and decisions/directions (the ‘one-to-many’ model). Trust and personal relationships are an essential part of the Al-Qaida network (a limiting factor, even while it provides enhanced security). Even while cell members are trained as ‘replaceable’ units, ‘vetting’ of members occurs during the invited training period under the observation of the core group.&lt;ref name=Sleepers&gt;{{cite web
 | url = http://www.metatempo.com/huntingthesleepers.pdf
 |format=PDF| title = Hunting the Sleepers: Tracking al-Qaida's Covert Operatives
 | date = 2001-12-31
 | author = Decision Support Systems, Inc.
 | accessdate = 2007-11-17
}}&lt;/ref&gt;

Cells of this structure are built outwards, from an internal leadership core. Superficially, this might be likened to a Western cell structure that emanates from a headquarters, but the Western centrality is bureaucratic, while structures in other non-western cultures builds on close personal relationships, often built over years, perhaps involving family or other in-group linkages. Such in-groups are thus extremely hard to infiltrate; infiltration has a serious chance only outside the in-group. Still, it may be possible for an in-group to be compromised through [[COMINT]] or, in rare cases, by compromising a member.

The core group is logically a ring, but is superimposed on an inner hub-and-spoke structure of ideological authority. Each member of the core forms another hub and spoke system (see [[#Infrastructure cells|infrastructure cells]]), the spokes leading to infrastructure cells under the supervision of the core group member, and possibly to operational groups which the headquarters support. Note that in this organization, there is a point at which the operational cell becomes autonomous of the core. Members surviving the operation may rejoin at various points.
[[Image:T-Cell-0.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

Osama, in this model, has the main responsibility of commanding the organization and being the spokesman on propaganda video and audio messages distributed by the propaganda cell. The other members of the core each command one or more infrastructure cells.

While the tight coupling enhances security, it can limit flexibility and the ability to scale the organization. This in-group, while sharing tight cultural and ideological values, is not committed to a bureaucratic process.

"Members of the core group are under what could be termed 'positive control'—long relationships
and similar mindsets make 'control' not so much of an issue, but there are distinct roles, and position (structural, financial, spiritual) determines authority, thus making the core group a hierarchy topologically.&lt;ref name=Sleepers /&gt;

In the first example of the core, each member knows how to reach two other members, and also knows the member(s) he considers his ideological superior. Solid lines show basic communication, dotted red arrows show the first level of ideological respect, and dotted blue arrows show a second level of ideological respect.

If Osama, the most respected, died, the core would reconstitute itself. While different members have an individual ideological guide, and these are not the same for all members, the core would reconstitute itself with Richard as most respected.

Assume there are no losses, and Osama can be reached directly only by members of the core group. Members of outer cells and support systems might know him only as "the Commander", or, as in the actual case of al-Qaeda, Osama bin Laden's face is recognizable worldwide, but only a few people know where he was or even how to contact him.

===Infrastructure cells===
Any clandestine or covert service, especially a non-national one, needs a variety of technical and administrative functions. Some of these services include:&lt;ref name=Sleepers /&gt;

# Forged documents and counterfeit currency
# Apartments and hiding places
# Communication means
# Transportation means
# Information
# Arms and ammunition
# Transport

Other functions include psychological operations, training, and finance.

A national intelligence service&lt;ref name=CIAsupport&gt;{{cite web
 | url = https://www.cia.gov/offices-of-cia/mission-support/who-we-are.html
 | author = US Central Intelligence Agency
 | title = Support to Mission: Who We Are
 | accessdate = 2007-11-19
}}&lt;/ref&gt;
has a support organization to deal with services such as finance, logistics, facilities (e.g., [[#Safehouses and Other Meeting Places|safehouses]]), information technology, communications, training, weapons and explosives, medical services, etc. Transportation alone is a huge function, including the need to buy tickets without drawing suspicion, and, where appropriate, using private vehicles. Finance includes the need to transfer money without coming under the suspicion of financial security organizations.

Some of these functions, such as finance, are far harder to operate in remote areas, such as the [[FATA]] of [[Pakistan]], than in cities with large numbers of official and unofficial financial institutions, and the communications to support them. If the financial office is distant from the remote headquarters, there is a need for [[couriers]], who must be trusted to some extent, but they may not know the contents of their messages or the actual identity of sender and/or receiver. The couriers, depending on the balance among type and size of message, security, and technology available, may memorize messages, carry audio or video recordings, or hand-carry computer media.
[[Image:T-Cell-1.png|thumb|Core group and infrastructure cells; military cells in training]]

"These cells are socially embedded (less so than the core group, however), structurally embedded, functionally embedded (they are specialized into a domain), and knowledge base-specific (there does not seem to be a great deal of cross-training, or lateral mobility in the organization). Such cells are probably subjected to a mixture of positive and negative control ("do this, do these sorts of things, don’t do that")."&lt;ref name=Sleepers /&gt;

{| class="wikitable"
&lt;caption&gt;Core Structure of Non-National Group&lt;/caption&gt;
|-
! Member
! Infrastructure commanded
|-
| Richard
| Finance
|-
| Anton
| Military training/operations 1
|-
| Hassan
| Military training/operations 2
|-
| David
| Transportation
|-
| Kim
| Communications and propaganda
|}

The leaders of military cells are responsible for training them, and, when an operation is scheduled, selecting the operational commander, giving him the basic objective and arranging whatever support is needed, and then release him from tight control to execute the meeting. Depending on the specific case, the military leaders might have direct, possibly one-way, communications with their cells, or they might have to give Kim the messages to be transmitted, by means that Anton and Hassan have no need to know.

Note that Anton does not have a direct connection to Kim. Under normal circumstances, he sacrifices efficiency for security, by passing communications requests through Hassan. The security structure also means that Hassan does not know the members of Anton's cells, and Kim may know only ways to communicate with them but not their identity.

Kim operates two systems of cells, one for secure communications and one for propaganda. To send out a propaganda message, Osama must pass it to Kim. If Kim were compromised, the core group might have significant problems with any sort of outside communications.

Terrorist networks do not match cleanly to other cell systems that regularly report to a headquarters. The apparent al-Qaeda methodology of letting operational cells decide on their final dates and means of attack exhibit an operational pattern, but not a periodicity that could easily be used for an [[Intelligence analysis management#Indications &amp; warning checklists|indications checklist]] appropriate for a warning center. Such lists depend on seeing a local pattern to give a specific warning.&lt;ref name=Vos&gt;{{cite web
 | title = Modeling Terrorist Networks - Complex Systems at the Mid-Range
 | first1 = Philip Vos
 | last1 = Fellman
 | first2 = Roxana
 | last2 = Wright
 | url = http://www.psych.lse.ac.uk/complexity/Conference/FellmanWright.pdf
 |format=PDF| accessdate = 2007-11-02
}}&lt;/ref&gt;

Note that Hassan has two subordinates that have not yet established operational cells. These subordinates can be considered '''sleepers''', but not necessarily with a sleeper cell.

===Operational cells===
For each mission are created one or more operational cells. If the al-Qaeda signature of multiple concurrent attacks is used, there may be an operational cell for each target location. It will depend on the operation if they will need any support cells in the operational area. For example, it may be more secure to have a local cell build bombs, which will be delivered by cells coming from outside the area.

"Operational cells are not created, but instead 'seeded' utilizing individuals spotted or that request assistance (both groups are 'vetted' by being trained under the observation of the core group, which dramatically restricts the opportunity for passing off walk-ins under false flag). Categorization of operational cells appears to be by capabilities, region, and then task/operation. Operational cells are composed of members whose worldview has been firmly tested—necessary to front-load, because such cells are dispersed back to their own local control (or negative control—proscribed behavior—with positive control only coming in the form of contact for synchronization or support)."&lt;ref name=Sleepers /&gt;

If operational cells routinely are "released" ''curved dotted lines on link to military cells'' to select their final operational parameters, they use a different paradigm than governmental clandestine or covert operations. On a number of cases, US special operations forces had to wait for Presidential authorization to make an attack, or even move to staging areas. Admittedly, a country would have to face the consequences of an inappropriate attack, so it may tend to be overcautious, where a terror network would merely shrug at the world being upset. Assuming that the al-Qaeda operational technique is not to use positive control, their operations may be more random, but also more unpredictable for counterterror forces. If their cells truly need constant control, there are communications links that might be detected by SIGINT, and if their command can be disrupted, the field units could not function. Since there is fairly little downside for terrorists to attack out of synchronization with other activities, the lack of positive control becomes a strength of their approach to cell organization.
[[Image:T-Cell-2.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

The operational cells need to have continuous internal communication; there is a commander, who may be in touch with infrastructure cells or, less likely from a security standpoint with the core group.

Al-Qaeda's approach, which even differs from that of earlier terrorist organizations, may be very viable for their goals:

* Cells are redundant and distributed, making them difficult to ‘roll up’
* Cells are coordinated, not under "command &amp; control"—this autonomy and local control makes them flexible, and enhances security
* Trust and comcon internally to the cell provide redundancy of potential command (a failure of Palestinian operations in the past), and well as a shared knowledgebase (which may mean, over time, that ‘cross training’ emerges inside a cell, providing redundancy of most critical skills and knowledge).&lt;ref name=Sleepers /&gt;

===Indirect support networks===
In the above graphic, note the indirect support network controlled by Richard's subcell.

"While Al-Qaida has elements of the organization designed to support the structure, but such elements are insufficient in meeting the needs of such an organization, and for security reasons there would be redundant and secondary-/tertiary-networks that are unaware of their connection to Al-Qaida. These networks, primarily related to fundraising and financial activities, as well as technology providers, are in a ‘use’ relationship with Al-Qaida—managed through cut-outs or individuals that do not inform them of the nature of activities, and that may have a cover pretext sufficient to deflect questions or inquiry."&lt;ref name=Sleepers /&gt;

===A possible countermeasure===
In 2002, ''U.S. News &amp; World Report'' said that American intelligence is beginning to acquire a sufficiently critical mass of intelligence on al-Qaida indicating, "Once thought nearly impossible to penetrate, al Qaeda is proving no tougher a target than the KGB or the Mafia--closed societies that took the U.S. government years to get inside. "We're getting names, the different camps they trained at, the hierarchy, the infighting," says an intelligence official. "It's very promising."&lt;ref name=Kaplan2002&gt;{{Cite journal
 | title = Run and Gun: Al Qaeda arrests and intelligence hauls bring new energy to the war on terrorism
 | first = David E. | last = Kaplan
 | date = 22 September 2002
 | journal = U.S. News &amp; World Report
 | url = http://www.usnews.com/usnews/news/articles/020930/archive_022824.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; The report also said that the collected data has allowed the recruiting of informants.

Writing in the U.S. Army journal ''Military Review'', David W. Pendall  suggested that a "catch-and-release program for suspected operatives might create reluctance or distrust in such suspects and prevent them from further acts or, perhaps more important, create distrust in the cell leaders of these individuals in the future." The author noted the press release describing Ramzi Binalshib's cooperation with the United States "are sure to prevent reentry into a terrorist cell as a trusted member and most likely limits the further trust and assignments of close cell associates still at large. The captor would determine when to name names and when to remain silent."&lt;ref name=Pendall2004&gt;{{Cite journal
 | date = January–February 2004
 | journal = Military Review
 | url = http://calldp.leavenworth.army.mil
 | first = David W. | last = Pendall
 | title =Effects-Based Operations and the Exercise of National Power
 | publisher = [[United States Army Combined Arms Center]]
 | postscript = &lt;!--None--&gt;
}}  Find the article by going through the Military Review directories&lt;/ref&gt; Indeed, once intelligence learns the name and characteristics of an at-large adversary, as well as some sensitive information that would plausibly be known to him, a news release could be issued to talk about his cooperation. Such a method could not be used too often, but, used carefully, could disturb the critical trust networks. The greatest uncertainty might be associated with throwing doubt onto a key member of an operational cell that has gone autonomous.

==See also==
* [[Leaderless resistance]]
* [[Lone wolf (terrorism)]]

==References==
{{reflist | 2}}

==External links==
* [http://theriskyshift.com/2012/06/an-introduction-to-terrorist-organisational-structures/ An Introduction To Terrorist Organisational Structures]

{{Intelligence cycle management}}

[[Category:Counter-intelligence]]
[[Category:Types of espionage]]
[[Category:Intelligence analysis]]
[[Category:Military intelligence]]
[[Category:Military tactics]]
[[Category:Secrecy]]
[[Category:Terrorism tactics]]

[http://www.cimacell.com/wiki Structure]</text>
    <sha1>7b3c2a89499405c85c9ff35d234f9d5187be2a33</sha1>
  </revision>
  <revision>
    <id>85</id>
    <parentid>84</parentid>
    <timestamp>2015-12-27T01:30:42Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39473" xml:space="preserve">{{for|the general use of a cellular structure by an organization, such as by a business|Cellular organization (disambiguation)}}
{{redirect|Sleeper cell}}
{{Use dmy dates|date=July 2011}}
{{multiple issues|
{{Essay-like|date=July 2011}}
{{POV|date=September 2012}}
{{Original research|date=January 2015}}
{{cleanup|reason=Poorly written, poorly referenced, marked essay-like (mostly user Hcberkowitz's edits; see page history) and POV issues and generally underlinked|date=January 2015}}
{{cleanup-rewrite|date=January 2015}}
{{Expert-subject|date=January 2015}}
}}

{{terrorism}}
A '''clandestine cell''' structure is a method for organizing a group of people like [[French resistance|resistance]] fighters or terrorists in such a way that it can more effectively resist penetration by an opposing organization (e.g., a law enforcement organization). In a cell structure, each small group of people in the cell only know the identities of the people in their cell; as such, if a cell member is apprehended and interrogated, he or she will not know the identities of the higher-ranking individuals in the organization. Depending on the group's [[philosophy]], its operational area, the communications technologies available, and the nature of the mission, it can range from a strict hierarchy to an extremely distributed organization. It is also a method used by [[organized crime|criminal organizations]], [[undercover]] operatives, and unconventional warfare (UW) units led by [[special forces]]. Historically, clandestine organizations have avoided electronic communications, because [[signals intelligence]] is a strength of conventional militaries and counterintelligence organizations.{{citation needed|date=August 2012}}

In the context of [[tradecraft]], [[covert operation|covert]] and [[clandestine operation|clandestine]] are not synonymous. As noted in the definition (which has been used by the United States and NATO since World War II) in a covert operation the identity of the sponsor is concealed, while in a clandestine operation the operation itself is concealed. Put differently, clandestine means "hidden", while covert means "deniable". The adversary is aware that a covert activity is happening, but does not know who is doing it, and certainly not their sponsorship. Clandestine activities, however, if successful, are completely unknown to the adversary, and their function, such as espionage, would be neutralized if there was any awareness of the activity.

A '''sleeper cell''' refers to a cell, or isolated grouping of [[sleeper agent]]s that lies dormant until it receives orders or decides to act.

==History==

=== Provisional Irish Republican Army===
As opposed to the [[French Resistance]], the modern [[Provisional Irish Republican Army]] (PIRA) has a history going back to Irish revolutionary forces in the early 20th century, but has little external control.  Its doctrine and organization have changed over time, given factors such as the independence of 26 of Ireland's 32 counties, the continued British control of Northern Ireland and the simple passage of time and changes in contemporary thinking and technology.&lt;ref name=Leahy&gt;{{cite web
 | url = http://cgsc.cdmhost.com/cgi-bin/showfile.exe?CISOROOT=/p4013coll2&amp;CISOPTR=386&amp;filename=387.pdf
 |format=PDF| author = Leahy, Kevin C.
 | year = 2005
 | title = The Impact of Technology on the Command, Control, and Organizational Structure of Insurgent Groups
 | accessdate=2007-12-04
}}&lt;/ref&gt;

Officially, the PIRA is hierarchical, but, especially as British security forces became more effective, changed to a semiautonomous model for its operational and certain of its support cells (e.g., transportation, intelligence, cover and security).&lt;ref name=GreenBook&gt;{{cite web
 | url = https://web.archive.org/web/20110606012137/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html
 | author = Irish Republican Army
 | title = The Green Book
 | accessdate=2007-12-04
|archiveurl=https://web.archive.org/web/20070616132240/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html|archivedate=2007-06-16}}&lt;/ref&gt; Its leadership sees itself as guiding and consensus-building. The lowest-level cells, typically of 2-5 people, tend to be built by people with an existing personal relationship. British counterinsurgents could fairly easily understand the command structure, but not the workings of the operational cells.

The IRA has an extensive network of inactive or sleeper cells, so new ''ad hoc'' organizations may appear for any specific operation.

===World War II French Resistance===
In World War II, [[Operation Jedburgh]] teams parachuted into occupied France to lead unconventional warfare units.&lt;ref name=Hall&gt;{{cite book
 | author = Hall, Roger
 | title = You're Stepping on my Cloak and Dagger
 | publisher = Bantam Books
 | year =1964
}}&lt;/ref&gt;&lt;ref name=SOETO&gt;{{cite book
 | chapterurl = http://www.history.army.mil/books/wwii/70-42/70-423.htm
 | chapter = Chapter 3: Special Operations in the European Theater
 | publisher = [[United States Army Center of Military History]]
| url = http://www.history.army.mil/books/wwii/70-42/70-42c.htm
| title = U.S. Army Special Operations in World War II
| first = David W.
| last = Hogan
| id = CMH Pub 70-42
|year = 1992
| location = Washington, D.C.
}}&lt;/ref&gt; They would be composed of two officers, one American or British, and the other French, the latter preferably from the area into which they landed. The third member of the team was a radio operator.

Especially through the French member, they would contact trusted individuals in the area of operation, and ask them to recruit a team of trusted subordinates (i.e., a subcell). If the team mission were sabotage, reconnaissance, or espionage, there was no need to meet in large units. If the team was to carry out direct action, often an unwise mission unless an appreciable number of the locals had military experience, it would be necessary to assemble into units for combat. Even then, the hideouts of the leadership were known only to subcell leaders. The legitimacy of the Jedburgh team came from its known affiliation with Allied powers, and it was a structure more appropriate for UW than for truly clandestine operations.

===National Front for the Liberation of South Vietnam===
Also known as the [[Viet Cong]], this organization grew from earlier anticolonial groups fighting the French, as well as anti-Japanese guerillas during World War II.&lt;ref name=VietCong&gt;{{cite book
 | author = Pike, Douglas
 | title = Viet Cong: Organization and Technique of the National Liberation Front of South Vietnam
 | publisher = MIT Press
 | year = 1970
}}&lt;/ref&gt;
Its command, control, and communication techniques derived from the experiences of these earlier insurgent groups. The group had extensive support from North Vietnam, and, indirectly, from the Soviet Union. It had parallel political and military structures, often overlapping. See [[Viet Cong and PAVN strategy and tactics]].
[[Image:Vcnvastructure4rev.jpg|thumb|right |A dual, but sometimes overlapping, Party and Military structure was top-down]]
The lowest level consisted of three-person cells who operated quite closely, and engaging in the sort of [[self-criticism]] common, as a bonding method, to Communist organizations.{{Citation needed|date=June 2014}}

==Parallel organizations==
The NLF and PIRA, as well as other movements, have chosen to have parallel political and military organizations. In the case of the NLF, other than some individuals with sanctuary in North Vietnam, the political organization could not be overt during the [[Vietnam War]]. After the war ended, surviving NLF officials held high office.

In the case of the PIRA, its political wing, [[Sinn Féin]], became increasingly overt, and then a full participant in politics. [[Hamas]] and [[Hezbollah]] also have variants of overt political/social service and covert military wings.

The overt political/social–covert military split avoided the inflexibility of a completely secret organization. Once an active insurgency began, the secrecy {{clarify span|could limit|date=January 2015}}&lt;!-- what? --&gt; freedom of action, distort information about goals and ideals, and restrict communication within the insurgency.&lt;ref name=FM3-24&gt;{{cite web
 | title = FM 3-24: Counterinsurgency
 | author = US Department of the Army
 |date=December 2006
 | url = https://fas.org/irp/doddir/army/fm3-24.pdf
|format=PDF}}&lt;/ref&gt; In a split organization, the public issues can be addressed overtly, while military actions were kept covert and intelligence functions stay clandestine.

==External support==
Many cell systems still receive, with due attention to security, support from the outside. This can range from leaders, trainers and supplies (such as the Jedburgh assistance to the French Resistance), or a safe haven for overt activities (such as the NLF spokesmen in Hanoi).

External support need not be overt. Certain Shi'a groups in Iraq, for example, do receive assistance from Iran{{Citation needed|date=March 2009}}, but this is not a public position of the government of Iran, and may even be limited to factions of that government.  Early US support to the Afghan Northern Alliance against the Taliban used clandestine operators from both the [[CIA]] and [[United States Army Special Forces]]. As the latter conflict escalated, the US participation became overt.

Note that both [[unconventional warfare]] (UW) (guerrilla operations) and [[foreign internal defense]] (FID) (counterinsurgency) may be covert and use cellular organization.

In a covert FID mission, only selected host nation (HN) leaders are aware of the foreign support organization. Under [[Operation White Star]], US personnel gave covert FID assistance to the Royal Lao Army starting in 1959, became overt in 1961, and ceased operations in 1962.

==Models of insurgency and associated cell characteristics==
While different kinds of insurgency differ in where they place clandestine or covert cells, when certain types of insurgency grow in power, the cell system is deemphasized. Cells still may be used for leadership security, but, if overt violence by organized units becomes significant, cells are less important. In Mao's three-stage doctrine,&lt;ref name=Mao1967&gt;{{cite book
 | title = On Protracted War
 | author = Mao,  Zedong | authorlink = Mao Zedong
 | year = 1967
 | publisher = Foreign Language Press, Beijing
}}&lt;/ref&gt; cells are still useful in Phase II to give cover to part-time guerillas, but, as the insurgency creates full-time military units in Phase III, the main units are the focus, not the cells. The [[Eighth Route Army]] did not run on a cell model.

When considering where cells exist with respect to the existing government, the type of insurgency needs to be considered. One US Army reference was Field Manual 100-20, which has been superseded by FM3-07.&lt;ref name=FM3-07&gt;{{cite web
 | title = FM 3-07 (formerly FM 100-20): Stability Operations and Support Operations
 | date = 20 February 2003
 | author = US Department of the Army
 | url = https://atiam.train.army.mil/soldierPortal/atia/adlsc/view/altfmt/9630-1
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; Drawing on this work, Nyberg (a [[United States Marine Corps]] officer) extended the ideas to describe four types of cell system, although his descriptions also encompass types of insurgencies that the cell system supports.&lt;ref name=Nyberg&gt;{{Cite journal
 | title = Insurgency: The Unsolved Mystery
 | first = Eric N. | last = Nyberg
 | publisher = US Marine Corps University Command and Staff College
 | year = 1991
 | url = http://www.globalsecurity.org/military/library/report/1991/NEN.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt;  At present, there is a new type associated with transnational terrorist insurgencies.

# Traditional: the slowest to form, this reflects a principally indigenous insurgency, initially with limited goals. It is more secure than others, as it tends to grow from people with social, cultural or family ties. The insurgents resent a government that has failed to recognize  tribal, racial, religious or linguistic groups "who perceive that the government has denied their rights and interests and work to establish or restore them. They seldom seek to overthrow the government or control the whole society; however, they frequently attempt to withdraw from government control through autonomy or semiautonomy." The Mujahideen in Afghanistan and the Kurdish revolt in Iraq illustrate the traditional pattern of insurgency. [[al-Qaeda]] generally operates in this mode, but if they become strong enough in a given area, they may change to the mass-oriented form.
# Subversive: Usually driven by an organization that contains at least some of the governing elite, some being sympathizers already in place, and others who penetrate the government. When they use violence, it has a specific purpose, such as coercing voters, intimidating officials, and disrupting and discrediting the government. Typically, there is a political arm (such as  [[Sinn Féin]] or the [[Viet Cong|National Liberation Front]]) that directs the military in planning carefully coordinated violence. "Employment of violence is designed to show the system to be incompetent and to provoke the government to an excessively violent response which further undermines its legitimacy." The [[Nazi]] rise to power, in the 1930s, is another example of subversion. Nazi members of parliament and street fighters were hardly clandestine, but the overall plan of the Nazi leadership to gain control of the nation was hidden. "A subversive insurgency is suited to a more permissive political environment which allows the insurgents to use both legal and illegal methods to accomplish their goals. Effective government resistance may convert this to a critical-cell model.
# Critical-cell: Critical cell is useful when the political climate becomes less permissive than one that allowed shadow cells. While other cell types try to form intelligence cells within the government, this type sets up "[[Continuity of government|shadow government]]" cells that can seize power once the system is destroyed both by external means and the internal subversion. This model fits the classic [[coup d'etat]],&lt;ref name=Luttwak&gt;{{cite book
 | title = Coup d'etat: A Practical Handbook
 | year = 1968
 | author = Luttwak, Edward | authorlink = Edward Luttwak
 | publisher = Harvard University Press
}}&lt;/ref&gt; and often tries to minimize violence. Variants include the [[Sandinista]] takeover of an existing government weakened by external popular revolution. "Insurgents also seek to infiltrate the government's institutions, but their object is to destroy the system from within." Clandestine cells form inside the government. "The use of violence remains covert until the government is so weakened that the insurgency's superior organization seizes power, supported by the armed force. One variation of this pattern is when the insurgent leadership permits the popular revolution to destroy the existing government, then emerges to direct the formation of a new government. Another variation is seen in the [[Cuba]]n revolution&lt;ref name=Guevara&gt;{{cite book
 | author = Guevara, Ernesto "Che"
 | title = On Guerilla Warfare
 | publisher = Praeger
 | year = 1961
}}&lt;/ref&gt; and is referred to as the foco (or Cuban model) insurgency. This model involves a single, armed cell which emerges in the midst of degenerating government legitimacy and becomes the nucleus around which mass popular support rallies.  The insurgents use this support to establish control and erect new institutions."
# Mass-oriented: where the subversive and covert-cell systems work from within the government, the mass-oriented builds a government completely outside the existing one, with the intention of replacing it. Such "insurgents patiently construct a base of passive and active political supporters, while simultaneously building a large armed element of guerrilla and regular forces.  They plan a protracted campaign of increasing violence to destroy the government and its institutions from the outside.  They have a well-developed ideology and carefully determine their objectives.  They are highly organized and effectively use propaganda and guerrilla action to mobilize forces for a direct political and military challenge to the government." The revolution that produced the [[Peoples' Republic of China]], the [[American Revolution]], and the [[Shining Path]] insurgency in Peru are examples of the mass-oriented model. Once established, this type of insurgency is extremely difficult to defeat because of its great depth of organization.

==Classic models for cell system operations==
Different kinds of cell organizations have been used for different purposes. This section focuses on clandestine cells, as would be used for [[espionage]], [[sabotage]], or the organization for [[unconventional warfare]]. When unconventional warfare starts using overt units, the cell system tends to be used only for sensitive leadership and intelligence roles.&lt;ref name=Mao1967 /&gt; The examples here will use [[CIA cryptonym]]s as a naming convention used to identify members of the cell system. Cryptonyms begin with a two-letter country or subject name (e.g., AL), followed with an arbitrary word. It is considered elegant to have the code merge with the other letters to form a pronounceable word.

===Operations under official cover===
Station BERRY operates, for country B, in target country BE. It has three case officers and several support officers. Espionage operation run by case officers under diplomatic cover, they would have to with the basic recruiting methods described in this article. Case officer BETTY runs the local agents BEN and BEATLE. Case officer BESSIE runs BENSON and BEAGLE.
[[Image:Wdip-Cell-0.png|thumb|Representative diplomatic-cover station and networks]]

Some recruits, due to the sensitivity of their position or their personalities not being appropriate for cell leadership, might not enter cells but be run as singletons, perhaps by other than the recruiting case officer. Asset BARD is a different sort of highly sensitive singleton, who is a joint asset of the country B, and the country identified by prefix AR. ARNOLD is a case officer from the country AR embassy, who knows only the case officer BERTRAM and the security officer BEST. ARNOLD does not know the station chief of BERRY or any of its other personnel. Other than BELL and BEST, the Station personnel only know BERTRAM as someone authorized to be in the Station, and who is known for his piano playing at embassy parties. He is covered as Cultural Attache, in a country that has very few pianos. Only the personnel involved with BARD know that ARNOLD is other than another friendly diplomat.

In contrast, BESSIE and BETTY know one another, and procedures exist for their taking over each other's assets in the event one of the two is disabled.

Some recruits, however, would be qualified to recruit their own subcell, as BEATLE has done. BESSIE knows the identity of BEATLE-1 and BEATLE-2, since he had them checked by headquarters counterintelligence before they were recruited. Note that a cryptonym does not imply anything about its  designee, such as gender.

===Clandestine presence===
The diagram of "initial team presence" shows that two teams, ALAN and ALICE, have successfully entered an area of operation, the country coded AL, but are only aware of a pool of potential recruits, and have not yet actually recruited anyone. They communicate with one another only through headquarters, so compromise of one team will not affect the other.
[[Image:Wnoc-Cell-0.png|thumb|left |Initial team presence by 2 separate clandestine teams with no official cover]]

Assume that in team ALAN, ALASTAIR is one of the officers with local contacts, might recruit two cell leaders, ALPINE and ALTITUDE. The other local officer in the team, ALBERT, recruits ALLOVER.  When ALPINE recruited two subcell members, they would be referred to as ALPINE-1 and ALPINE-2.

ALPINE and ALTITUDE only know how to reach ALASTAIR, but they are aware of at least some of other team members' identity should ALASTAIR be unavailable, and they would accept a message from ALBERT. Most often, the identity (and location) of the radio operator may not be shared. ALPINE and ALTITUDE, however, do not know one another. They do not know any of the members of team ALICE.

The legitimacy of the subcell structure came from the recruitment process, originally by the case officer and then by the cell leaders. Sometimes, the cell leader would propose subcell member names to the case officer, so the case officer could have a headquarters name check run before bringing the individual into the subcell. In principle, however, the subcell members would know ALPINE, and sometimes the other members of the ALPINE cell if they needed to work together; if ALPINE-1 and ALPINE-2 had independent assignments, they might not know each other. ALPINE-1 and ALPINE-2 certainly would not know ALASTAIR or anyone in the ALTITUDE or ALLOVER cells.
[[Image:Wnoc-Cell-1.png|thumb|Clandestine teams have built initial subcells]]

As the networks grow, a subcell leader might create his own cell, so ALPINE-2 might become the leader of the ALIMONY cell.

===Fault-tolerant cellular structures===
Modern communications theory has introduced methods to increase fault tolerance in cell organizations. In the past, if cell members only knew the cell leader, and the leader was neutralized, the cell was cut off from the rest of the organization. Game theory and graph theory have been applied to the study of optimal covert network design (see Lindelauf, R.H.A. et al. 2009. The influence of secrecy on the communication structure of covert networks. Social Networks 31: 126-137).

If a traditional cell had independent communications with the foreign support organization, headquarters might be able to arrange its reconnection. Another method is to have impersonal communications "side links" between cells, such as a pair of [[dead drop]]s, one for Team ALAN to leave "lost contact" messages to be retrieved by Team ALICE, and another dead drop for Team ALICE to leave messages for Team ALAN.

These links, to be used only on losing contact, do not guarantee a contact. When a team finds a message in its emergency drop, it might do no more than send an alert message to headquarters. Headquarters might determine, through [[SIGINT]] or other sources, that the enemy had captured the leadership and the entire team, and order the other team not to attempt contact. If headquarters can have reasonable confidence that there is a communications failure or partial compromise, it might send a new contact to the survivors.

When the cut-off team has electronic communications, such as the Internet, it has a much better chance of eluding surveillance and getting emergency instructions than by using a dead drop that can be under physical surveillance.

==Non-traditional models, exemplified by al-Qaeda==
Due to cultural differences, assuming the ''al-Qaeda Training Manual''&lt;ref name=AQTM&gt;{{cite web
 | url = https://fas.org/irp/world/para/aqmanual.pdf
 |format=PDF| title = al-Qaeda training manual
 | publisher = US Southern District Court, US New York City Attorney's Office, entered as evidence in Africa embassy bombings
}}&lt;/ref&gt; is authentic, eastern cell structures may differ from the Western mode. "Al-Qaida's minimal core group, only accounting for the leadership, can also be viewed topologically as a ring or chain network, with each leader/node heading their own particular hierarchy.

"Such networks function by having their sub-networks provide information and other forms of support (the ‘many-to-one’ model), while the core group supplies ‘truth’ and decisions/directions (the ‘one-to-many’ model). Trust and personal relationships are an essential part of the Al-Qaida network (a limiting factor, even while it provides enhanced security). Even while cell members are trained as ‘replaceable’ units, ‘vetting’ of members occurs during the invited training period under the observation of the core group.&lt;ref name=Sleepers&gt;{{cite web
 | url = http://www.metatempo.com/huntingthesleepers.pdf
 |format=PDF| title = Hunting the Sleepers: Tracking al-Qaida's Covert Operatives
 | date = 2001-12-31
 | author = Decision Support Systems, Inc.
 | accessdate = 2007-11-17
}}&lt;/ref&gt;

Cells of this structure are built outwards, from an internal leadership core. Superficially, this might be likened to a Western cell structure that emanates from a headquarters, but the Western centrality is bureaucratic, while structures in other non-western cultures builds on close personal relationships, often built over years, perhaps involving family or other in-group linkages. Such in-groups are thus extremely hard to infiltrate; infiltration has a serious chance only outside the in-group. Still, it may be possible for an in-group to be compromised through [[COMINT]] or, in rare cases, by compromising a member.

The core group is logically a ring, but is superimposed on an inner hub-and-spoke structure of ideological authority. Each member of the core forms another hub and spoke system (see [[#Infrastructure cells|infrastructure cells]]), the spokes leading to infrastructure cells under the supervision of the core group member, and possibly to operational groups which the headquarters support. Note that in this organization, there is a point at which the operational cell becomes autonomous of the core. Members surviving the operation may rejoin at various points.
[[Image:T-Cell-0.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

Osama, in this model, has the main responsibility of commanding the organization and being the spokesman on propaganda video and audio messages distributed by the propaganda cell. The other members of the core each command one or more infrastructure cells.

While the tight coupling enhances security, it can limit flexibility and the ability to scale the organization. This in-group, while sharing tight cultural and ideological values, is not committed to a bureaucratic process.

"Members of the core group are under what could be termed 'positive control'—long relationships
and similar mindsets make 'control' not so much of an issue, but there are distinct roles, and position (structural, financial, spiritual) determines authority, thus making the core group a hierarchy topologically.&lt;ref name=Sleepers /&gt;

In the first example of the core, each member knows how to reach two other members, and also knows the member(s) he considers his ideological superior. Solid lines show basic communication, dotted red arrows show the first level of ideological respect, and dotted blue arrows show a second level of ideological respect.

If Osama, the most respected, died, the core would reconstitute itself. While different members have an individual ideological guide, and these are not the same for all members, the core would reconstitute itself with Richard as most respected.

Assume there are no losses, and Osama can be reached directly only by members of the core group. Members of outer cells and support systems might know him only as "the Commander", or, as in the actual case of al-Qaeda, Osama bin Laden's face is recognizable worldwide, but only a few people know where he was or even how to contact him.

===Infrastructure cells===
Any clandestine or covert service, especially a non-national one, needs a variety of technical and administrative functions. Some of these services include:&lt;ref name=Sleepers /&gt;

# Forged documents and counterfeit currency
# Apartments and hiding places
# Communication means
# Transportation means
# Information
# Arms and ammunition
# Transport

Other functions include psychological operations, training, and finance.

A national intelligence service&lt;ref name=CIAsupport&gt;{{cite web
 | url = https://www.cia.gov/offices-of-cia/mission-support/who-we-are.html
 | author = US Central Intelligence Agency
 | title = Support to Mission: Who We Are
 | accessdate = 2007-11-19
}}&lt;/ref&gt;
has a support organization to deal with services such as finance, logistics, facilities (e.g., [[#Safehouses and Other Meeting Places|safehouses]]), information technology, communications, training, weapons and explosives, medical services, etc. Transportation alone is a huge function, including the need to buy tickets without drawing suspicion, and, where appropriate, using private vehicles. Finance includes the need to transfer money without coming under the suspicion of financial security organizations.

Some of these functions, such as finance, are far harder to operate in remote areas, such as the [[FATA]] of [[Pakistan]], than in cities with large numbers of official and unofficial financial institutions, and the communications to support them. If the financial office is distant from the remote headquarters, there is a need for [[couriers]], who must be trusted to some extent, but they may not know the contents of their messages or the actual identity of sender and/or receiver. The couriers, depending on the balance among type and size of message, security, and technology available, may memorize messages, carry audio or video recordings, or hand-carry computer media.
[[Image:T-Cell-1.png|thumb|Core group and infrastructure cells; military cells in training]]

"These cells are socially embedded (less so than the core group, however), structurally embedded, functionally embedded (they are specialized into a domain), and knowledge base-specific (there does not seem to be a great deal of cross-training, or lateral mobility in the organization). Such cells are probably subjected to a mixture of positive and negative control ("do this, do these sorts of things, don’t do that")."&lt;ref name=Sleepers /&gt;

{| class="wikitable"
&lt;caption&gt;Core Structure of Non-National Group&lt;/caption&gt;
|-
! Member
! Infrastructure commanded
|-
| Richard
| Finance
|-
| Anton
| Military training/operations 1
|-
| Hassan
| Military training/operations 2
|-
| David
| Transportation
|-
| Kim
| Communications and propaganda
|}

The leaders of military cells are responsible for training them, and, when an operation is scheduled, selecting the operational commander, giving him the basic objective and arranging whatever support is needed, and then release him from tight control to execute the meeting. Depending on the specific case, the military leaders might have direct, possibly one-way, communications with their cells, or they might have to give Kim the messages to be transmitted, by means that Anton and Hassan have no need to know.

Note that Anton does not have a direct connection to Kim. Under normal circumstances, he sacrifices efficiency for security, by passing communications requests through Hassan. The security structure also means that Hassan does not know the members of Anton's cells, and Kim may know only ways to communicate with them but not their identity.

Kim operates two systems of cells, one for secure communications and one for propaganda. To send out a propaganda message, Osama must pass it to Kim. If Kim were compromised, the core group might have significant problems with any sort of outside communications.

Terrorist networks do not match cleanly to other cell systems that regularly report to a headquarters. The apparent al-Qaeda methodology of letting operational cells decide on their final dates and means of attack exhibit an operational pattern, but not a periodicity that could easily be used for an [[Intelligence analysis management#Indications &amp; warning checklists|indications checklist]] appropriate for a warning center. Such lists depend on seeing a local pattern to give a specific warning.&lt;ref name=Vos&gt;{{cite web
 | title = Modeling Terrorist Networks - Complex Systems at the Mid-Range
 | first1 = Philip Vos
 | last1 = Fellman
 | first2 = Roxana
 | last2 = Wright
 | url = http://www.psych.lse.ac.uk/complexity/Conference/FellmanWright.pdf
 |format=PDF| accessdate = 2007-11-02
}}&lt;/ref&gt;

Note that Hassan has two subordinates that have not yet established operational cells. These subordinates can be considered '''sleepers''', but not necessarily with a sleeper cell.

===Operational cells===
For each mission are created one or more operational cells. If the al-Qaeda signature of multiple concurrent attacks is used, there may be an operational cell for each target location. It will depend on the operation if they will need any support cells in the operational area. For example, it may be more secure to have a local cell build bombs, which will be delivered by cells coming from outside the area.

"Operational cells are not created, but instead 'seeded' utilizing individuals spotted or that request assistance (both groups are 'vetted' by being trained under the observation of the core group, which dramatically restricts the opportunity for passing off walk-ins under false flag). Categorization of operational cells appears to be by capabilities, region, and then task/operation. Operational cells are composed of members whose worldview has been firmly tested—necessary to front-load, because such cells are dispersed back to their own local control (or negative control—proscribed behavior—with positive control only coming in the form of contact for synchronization or support)."&lt;ref name=Sleepers /&gt;

If operational cells routinely are "released" ''curved dotted lines on link to military cells'' to select their final operational parameters, they use a different paradigm than governmental clandestine or covert operations. On a number of cases, US special operations forces had to wait for Presidential authorization to make an attack, or even move to staging areas. Admittedly, a country would have to face the consequences of an inappropriate attack, so it may tend to be overcautious, where a terror network would merely shrug at the world being upset. Assuming that the al-Qaeda operational technique is not to use positive control, their operations may be more random, but also more unpredictable for counterterror forces. If their cells truly need constant control, there are communications links that might be detected by SIGINT, and if their command can be disrupted, the field units could not function. Since there is fairly little downside for terrorists to attack out of synchronization with other activities, the lack of positive control becomes a strength of their approach to cell organization.
[[Image:T-Cell-2.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

The operational cells need to have continuous internal communication; there is a commander, who may be in touch with infrastructure cells or, less likely from a security standpoint with the core group.

Al-Qaeda's approach, which even differs from that of earlier terrorist organizations, may be very viable for their goals:

* Cells are redundant and distributed, making them difficult to ‘roll up’
* Cells are coordinated, not under "command &amp; control"—this autonomy and local control makes them flexible, and enhances security
* Trust and comcon internally to the cell provide redundancy of potential command (a failure of Palestinian operations in the past), and well as a shared knowledgebase (which may mean, over time, that ‘cross training’ emerges inside a cell, providing redundancy of most critical skills and knowledge).&lt;ref name=Sleepers /&gt;

===Indirect support networks===
In the above graphic, note the indirect support network controlled by Richard's subcell.

"While Al-Qaida has elements of the organization designed to support the structure, but such elements are insufficient in meeting the needs of such an organization, and for security reasons there would be redundant and secondary-/tertiary-networks that are unaware of their connection to Al-Qaida. These networks, primarily related to fundraising and financial activities, as well as technology providers, are in a ‘use’ relationship with Al-Qaida—managed through cut-outs or individuals that do not inform them of the nature of activities, and that may have a cover pretext sufficient to deflect questions or inquiry."&lt;ref name=Sleepers /&gt;

===A possible countermeasure===
In 2002, ''U.S. News &amp; World Report'' said that American intelligence is beginning to acquire a sufficiently critical mass of intelligence on al-Qaida indicating, "Once thought nearly impossible to penetrate, al Qaeda is proving no tougher a target than the KGB or the Mafia--closed societies that took the U.S. government years to get inside. "We're getting names, the different camps they trained at, the hierarchy, the infighting," says an intelligence official. "It's very promising."&lt;ref name=Kaplan2002&gt;{{Cite journal
 | title = Run and Gun: Al Qaeda arrests and intelligence hauls bring new energy to the war on terrorism
 | first = David E. | last = Kaplan
 | date = 22 September 2002
 | journal = U.S. News &amp; World Report
 | url = http://www.usnews.com/usnews/news/articles/020930/archive_022824.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; The report also said that the collected data has allowed the recruiting of informants.

Writing in the U.S. Army journal ''Military Review'', David W. Pendall  suggested that a "catch-and-release program for suspected operatives might create reluctance or distrust in such suspects and prevent them from further acts or, perhaps more important, create distrust in the cell leaders of these individuals in the future." The author noted the press release describing Ramzi Binalshib's cooperation with the United States "are sure to prevent reentry into a terrorist cell as a trusted member and most likely limits the further trust and assignments of close cell associates still at large. The captor would determine when to name names and when to remain silent."&lt;ref name=Pendall2004&gt;{{Cite journal
 | date = January–February 2004
 | journal = Military Review
 | url = http://calldp.leavenworth.army.mil
 | first = David W. | last = Pendall
 | title =Effects-Based Operations and the Exercise of National Power
 | publisher = [[United States Army Combined Arms Center]]
 | postscript = &lt;!--None--&gt;
}}  Find the article by going through the Military Review directories&lt;/ref&gt; Indeed, once intelligence learns the name and characteristics of an at-large adversary, as well as some sensitive information that would plausibly be known to him, a news release could be issued to talk about his cooperation. Such a method could not be used too often, but, used carefully, could disturb the critical trust networks. The greatest uncertainty might be associated with throwing doubt onto a key member of an operational cell that has gone autonomous.

==See also==
* [[Leaderless resistance]]
* [[Lone wolf (terrorism)]]

==References==
{{reflist | 2}}

==External links==
* [http://theriskyshift.com/2012/06/an-introduction-to-terrorist-organisational-structures/ An Introduction To Terrorist Organisational Structures]

{{Intelligence cycle management}}

[[Category:Counter-intelligence]]
[[Category:Types of espionage]]
[[Category:Intelligence analysis]]
[[Category:Military intelligence]]
[[Category:Military tactics]]
[[Category:Secrecy]]
[[Category:Terrorism tactics]]

[http:/www.cimacell.com/wiki/index.php?title=Structure Reachback Operations]</text>
    <sha1>73f8623863babfda3c289283fb63f2ac68a72d71</sha1>
  </revision>
  <revision>
    <id>86</id>
    <parentid>85</parentid>
    <timestamp>2015-12-27T01:32:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39468" xml:space="preserve">{{for|the general use of a cellular structure by an organization, such as by a business|Cellular organization (disambiguation)}}
{{redirect|Sleeper cell}}
{{Use dmy dates|date=July 2011}}
{{multiple issues|
{{Essay-like|date=July 2011}}
{{POV|date=September 2012}}
{{Original research|date=January 2015}}
{{cleanup|reason=Poorly written, poorly referenced, marked essay-like (mostly user Hcberkowitz's edits; see page history) and POV issues and generally underlinked|date=January 2015}}
{{cleanup-rewrite|date=January 2015}}
{{Expert-subject|date=January 2015}}
}}

{{terrorism}}
A '''clandestine cell''' structure is a method for organizing a group of people like [[French resistance|resistance]] fighters or terrorists in such a way that it can more effectively resist penetration by an opposing organization (e.g., a law enforcement organization). In a cell structure, each small group of people in the cell only know the identities of the people in their cell; as such, if a cell member is apprehended and interrogated, he or she will not know the identities of the higher-ranking individuals in the organization. Depending on the group's [[philosophy]], its operational area, the communications technologies available, and the nature of the mission, it can range from a strict hierarchy to an extremely distributed organization. It is also a method used by [[organized crime|criminal organizations]], [[undercover]] operatives, and unconventional warfare (UW) units led by [[special forces]]. Historically, clandestine organizations have avoided electronic communications, because [[signals intelligence]] is a strength of conventional militaries and counterintelligence organizations.{{citation needed|date=August 2012}}

In the context of [[tradecraft]], [[covert operation|covert]] and [[clandestine operation|clandestine]] are not synonymous. As noted in the definition (which has been used by the United States and NATO since World War II) in a covert operation the identity of the sponsor is concealed, while in a clandestine operation the operation itself is concealed. Put differently, clandestine means "hidden", while covert means "deniable". The adversary is aware that a covert activity is happening, but does not know who is doing it, and certainly not their sponsorship. Clandestine activities, however, if successful, are completely unknown to the adversary, and their function, such as espionage, would be neutralized if there was any awareness of the activity.

A '''sleeper cell''' refers to a cell, or isolated grouping of [[sleeper agent]]s that lies dormant until it receives orders or decides to act.

==History==

=== Provisional Irish Republican Army===
As opposed to the [[French Resistance]], the modern [[Provisional Irish Republican Army]] (PIRA) has a history going back to Irish revolutionary forces in the early 20th century, but has little external control.  Its doctrine and organization have changed over time, given factors such as the independence of 26 of Ireland's 32 counties, the continued British control of Northern Ireland and the simple passage of time and changes in contemporary thinking and technology.&lt;ref name=Leahy&gt;{{cite web
 | url = http://cgsc.cdmhost.com/cgi-bin/showfile.exe?CISOROOT=/p4013coll2&amp;CISOPTR=386&amp;filename=387.pdf
 |format=PDF| author = Leahy, Kevin C.
 | year = 2005
 | title = The Impact of Technology on the Command, Control, and Organizational Structure of Insurgent Groups
 | accessdate=2007-12-04
}}&lt;/ref&gt;

Officially, the PIRA is hierarchical, but, especially as British security forces became more effective, changed to a semiautonomous model for its operational and certain of its support cells (e.g., transportation, intelligence, cover and security).&lt;ref name=GreenBook&gt;{{cite web
 | url = https://web.archive.org/web/20110606012137/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html
 | author = Irish Republican Army
 | title = The Green Book
 | accessdate=2007-12-04
|archiveurl=https://web.archive.org/web/20070616132240/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html|archivedate=2007-06-16}}&lt;/ref&gt; Its leadership sees itself as guiding and consensus-building. The lowest-level cells, typically of 2-5 people, tend to be built by people with an existing personal relationship. British counterinsurgents could fairly easily understand the command structure, but not the workings of the operational cells.

The IRA has an extensive network of inactive or sleeper cells, so new ''ad hoc'' organizations may appear for any specific operation.

===World War II French Resistance===
In World War II, [[Operation Jedburgh]] teams parachuted into occupied France to lead unconventional warfare units.&lt;ref name=Hall&gt;{{cite book
 | author = Hall, Roger
 | title = You're Stepping on my Cloak and Dagger
 | publisher = Bantam Books
 | year =1964
}}&lt;/ref&gt;&lt;ref name=SOETO&gt;{{cite book
 | chapterurl = http://www.history.army.mil/books/wwii/70-42/70-423.htm
 | chapter = Chapter 3: Special Operations in the European Theater
 | publisher = [[United States Army Center of Military History]]
| url = http://www.history.army.mil/books/wwii/70-42/70-42c.htm
| title = U.S. Army Special Operations in World War II
| first = David W.
| last = Hogan
| id = CMH Pub 70-42
|year = 1992
| location = Washington, D.C.
}}&lt;/ref&gt; They would be composed of two officers, one American or British, and the other French, the latter preferably from the area into which they landed. The third member of the team was a radio operator.

Especially through the French member, they would contact trusted individuals in the area of operation, and ask them to recruit a team of trusted subordinates (i.e., a subcell). If the team mission were sabotage, reconnaissance, or espionage, there was no need to meet in large units. If the team was to carry out direct action, often an unwise mission unless an appreciable number of the locals had military experience, it would be necessary to assemble into units for combat. Even then, the hideouts of the leadership were known only to subcell leaders. The legitimacy of the Jedburgh team came from its known affiliation with Allied powers, and it was a structure more appropriate for UW than for truly clandestine operations.

===National Front for the Liberation of South Vietnam===
Also known as the [[Viet Cong]], this organization grew from earlier anticolonial groups fighting the French, as well as anti-Japanese guerillas during World War II.&lt;ref name=VietCong&gt;{{cite book
 | author = Pike, Douglas
 | title = Viet Cong: Organization and Technique of the National Liberation Front of South Vietnam
 | publisher = MIT Press
 | year = 1970
}}&lt;/ref&gt;
Its command, control, and communication techniques derived from the experiences of these earlier insurgent groups. The group had extensive support from North Vietnam, and, indirectly, from the Soviet Union. It had parallel political and military structures, often overlapping. See [[Viet Cong and PAVN strategy and tactics]].
[[Image:Vcnvastructure4rev.jpg|thumb|right |A dual, but sometimes overlapping, Party and Military structure was top-down]]
The lowest level consisted of three-person cells who operated quite closely, and engaging in the sort of [[self-criticism]] common, as a bonding method, to Communist organizations.{{Citation needed|date=June 2014}}

==Parallel organizations==
The NLF and PIRA, as well as other movements, have chosen to have parallel political and military organizations. In the case of the NLF, other than some individuals with sanctuary in North Vietnam, the political organization could not be overt during the [[Vietnam War]]. After the war ended, surviving NLF officials held high office.

In the case of the PIRA, its political wing, [[Sinn Féin]], became increasingly overt, and then a full participant in politics. [[Hamas]] and [[Hezbollah]] also have variants of overt political/social service and covert military wings.

The overt political/social–covert military split avoided the inflexibility of a completely secret organization. Once an active insurgency began, the secrecy {{clarify span|could limit|date=January 2015}}&lt;!-- what? --&gt; freedom of action, distort information about goals and ideals, and restrict communication within the insurgency.&lt;ref name=FM3-24&gt;{{cite web
 | title = FM 3-24: Counterinsurgency
 | author = US Department of the Army
 |date=December 2006
 | url = https://fas.org/irp/doddir/army/fm3-24.pdf
|format=PDF}}&lt;/ref&gt; In a split organization, the public issues can be addressed overtly, while military actions were kept covert and intelligence functions stay clandestine.

==External support==
Many cell systems still receive, with due attention to security, support from the outside. This can range from leaders, trainers and supplies (such as the Jedburgh assistance to the French Resistance), or a safe haven for overt activities (such as the NLF spokesmen in Hanoi).

External support need not be overt. Certain Shi'a groups in Iraq, for example, do receive assistance from Iran{{Citation needed|date=March 2009}}, but this is not a public position of the government of Iran, and may even be limited to factions of that government.  Early US support to the Afghan Northern Alliance against the Taliban used clandestine operators from both the [[CIA]] and [[United States Army Special Forces]]. As the latter conflict escalated, the US participation became overt.

Note that both [[unconventional warfare]] (UW) (guerrilla operations) and [[foreign internal defense]] (FID) (counterinsurgency) may be covert and use cellular organization.

In a covert FID mission, only selected host nation (HN) leaders are aware of the foreign support organization. Under [[Operation White Star]], US personnel gave covert FID assistance to the Royal Lao Army starting in 1959, became overt in 1961, and ceased operations in 1962.

==Models of insurgency and associated cell characteristics==
While different kinds of insurgency differ in where they place clandestine or covert cells, when certain types of insurgency grow in power, the cell system is deemphasized. Cells still may be used for leadership security, but, if overt violence by organized units becomes significant, cells are less important. In Mao's three-stage doctrine,&lt;ref name=Mao1967&gt;{{cite book
 | title = On Protracted War
 | author = Mao,  Zedong | authorlink = Mao Zedong
 | year = 1967
 | publisher = Foreign Language Press, Beijing
}}&lt;/ref&gt; cells are still useful in Phase II to give cover to part-time guerillas, but, as the insurgency creates full-time military units in Phase III, the main units are the focus, not the cells. The [[Eighth Route Army]] did not run on a cell model.

When considering where cells exist with respect to the existing government, the type of insurgency needs to be considered. One US Army reference was Field Manual 100-20, which has been superseded by FM3-07.&lt;ref name=FM3-07&gt;{{cite web
 | title = FM 3-07 (formerly FM 100-20): Stability Operations and Support Operations
 | date = 20 February 2003
 | author = US Department of the Army
 | url = https://atiam.train.army.mil/soldierPortal/atia/adlsc/view/altfmt/9630-1
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; Drawing on this work, Nyberg (a [[United States Marine Corps]] officer) extended the ideas to describe four types of cell system, although his descriptions also encompass types of insurgencies that the cell system supports.&lt;ref name=Nyberg&gt;{{Cite journal
 | title = Insurgency: The Unsolved Mystery
 | first = Eric N. | last = Nyberg
 | publisher = US Marine Corps University Command and Staff College
 | year = 1991
 | url = http://www.globalsecurity.org/military/library/report/1991/NEN.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt;  At present, there is a new type associated with transnational terrorist insurgencies.

# Traditional: the slowest to form, this reflects a principally indigenous insurgency, initially with limited goals. It is more secure than others, as it tends to grow from people with social, cultural or family ties. The insurgents resent a government that has failed to recognize  tribal, racial, religious or linguistic groups "who perceive that the government has denied their rights and interests and work to establish or restore them. They seldom seek to overthrow the government or control the whole society; however, they frequently attempt to withdraw from government control through autonomy or semiautonomy." The Mujahideen in Afghanistan and the Kurdish revolt in Iraq illustrate the traditional pattern of insurgency. [[al-Qaeda]] generally operates in this mode, but if they become strong enough in a given area, they may change to the mass-oriented form.
# Subversive: Usually driven by an organization that contains at least some of the governing elite, some being sympathizers already in place, and others who penetrate the government. When they use violence, it has a specific purpose, such as coercing voters, intimidating officials, and disrupting and discrediting the government. Typically, there is a political arm (such as  [[Sinn Féin]] or the [[Viet Cong|National Liberation Front]]) that directs the military in planning carefully coordinated violence. "Employment of violence is designed to show the system to be incompetent and to provoke the government to an excessively violent response which further undermines its legitimacy." The [[Nazi]] rise to power, in the 1930s, is another example of subversion. Nazi members of parliament and street fighters were hardly clandestine, but the overall plan of the Nazi leadership to gain control of the nation was hidden. "A subversive insurgency is suited to a more permissive political environment which allows the insurgents to use both legal and illegal methods to accomplish their goals. Effective government resistance may convert this to a critical-cell model.
# Critical-cell: Critical cell is useful when the political climate becomes less permissive than one that allowed shadow cells. While other cell types try to form intelligence cells within the government, this type sets up "[[Continuity of government|shadow government]]" cells that can seize power once the system is destroyed both by external means and the internal subversion. This model fits the classic [[coup d'etat]],&lt;ref name=Luttwak&gt;{{cite book
 | title = Coup d'etat: A Practical Handbook
 | year = 1968
 | author = Luttwak, Edward | authorlink = Edward Luttwak
 | publisher = Harvard University Press
}}&lt;/ref&gt; and often tries to minimize violence. Variants include the [[Sandinista]] takeover of an existing government weakened by external popular revolution. "Insurgents also seek to infiltrate the government's institutions, but their object is to destroy the system from within." Clandestine cells form inside the government. "The use of violence remains covert until the government is so weakened that the insurgency's superior organization seizes power, supported by the armed force. One variation of this pattern is when the insurgent leadership permits the popular revolution to destroy the existing government, then emerges to direct the formation of a new government. Another variation is seen in the [[Cuba]]n revolution&lt;ref name=Guevara&gt;{{cite book
 | author = Guevara, Ernesto "Che"
 | title = On Guerilla Warfare
 | publisher = Praeger
 | year = 1961
}}&lt;/ref&gt; and is referred to as the foco (or Cuban model) insurgency. This model involves a single, armed cell which emerges in the midst of degenerating government legitimacy and becomes the nucleus around which mass popular support rallies.  The insurgents use this support to establish control and erect new institutions."
# Mass-oriented: where the subversive and covert-cell systems work from within the government, the mass-oriented builds a government completely outside the existing one, with the intention of replacing it. Such "insurgents patiently construct a base of passive and active political supporters, while simultaneously building a large armed element of guerrilla and regular forces.  They plan a protracted campaign of increasing violence to destroy the government and its institutions from the outside.  They have a well-developed ideology and carefully determine their objectives.  They are highly organized and effectively use propaganda and guerrilla action to mobilize forces for a direct political and military challenge to the government." The revolution that produced the [[Peoples' Republic of China]], the [[American Revolution]], and the [[Shining Path]] insurgency in Peru are examples of the mass-oriented model. Once established, this type of insurgency is extremely difficult to defeat because of its great depth of organization.

==Classic models for cell system operations==
Different kinds of cell organizations have been used for different purposes. This section focuses on clandestine cells, as would be used for [[espionage]], [[sabotage]], or the organization for [[unconventional warfare]]. When unconventional warfare starts using overt units, the cell system tends to be used only for sensitive leadership and intelligence roles.&lt;ref name=Mao1967 /&gt; The examples here will use [[CIA cryptonym]]s as a naming convention used to identify members of the cell system. Cryptonyms begin with a two-letter country or subject name (e.g., AL), followed with an arbitrary word. It is considered elegant to have the code merge with the other letters to form a pronounceable word.

===Operations under official cover===
Station BERRY operates, for country B, in target country BE. It has three case officers and several support officers. Espionage operation run by case officers under diplomatic cover, they would have to with the basic recruiting methods described in this article. Case officer BETTY runs the local agents BEN and BEATLE. Case officer BESSIE runs BENSON and BEAGLE.
[[Image:Wdip-Cell-0.png|thumb|Representative diplomatic-cover station and networks]]

Some recruits, due to the sensitivity of their position or their personalities not being appropriate for cell leadership, might not enter cells but be run as singletons, perhaps by other than the recruiting case officer. Asset BARD is a different sort of highly sensitive singleton, who is a joint asset of the country B, and the country identified by prefix AR. ARNOLD is a case officer from the country AR embassy, who knows only the case officer BERTRAM and the security officer BEST. ARNOLD does not know the station chief of BERRY or any of its other personnel. Other than BELL and BEST, the Station personnel only know BERTRAM as someone authorized to be in the Station, and who is known for his piano playing at embassy parties. He is covered as Cultural Attache, in a country that has very few pianos. Only the personnel involved with BARD know that ARNOLD is other than another friendly diplomat.

In contrast, BESSIE and BETTY know one another, and procedures exist for their taking over each other's assets in the event one of the two is disabled.

Some recruits, however, would be qualified to recruit their own subcell, as BEATLE has done. BESSIE knows the identity of BEATLE-1 and BEATLE-2, since he had them checked by headquarters counterintelligence before they were recruited. Note that a cryptonym does not imply anything about its  designee, such as gender.

===Clandestine presence===
The diagram of "initial team presence" shows that two teams, ALAN and ALICE, have successfully entered an area of operation, the country coded AL, but are only aware of a pool of potential recruits, and have not yet actually recruited anyone. They communicate with one another only through headquarters, so compromise of one team will not affect the other.
[[Image:Wnoc-Cell-0.png|thumb|left |Initial team presence by 2 separate clandestine teams with no official cover]]

Assume that in team ALAN, ALASTAIR is one of the officers with local contacts, might recruit two cell leaders, ALPINE and ALTITUDE. The other local officer in the team, ALBERT, recruits ALLOVER.  When ALPINE recruited two subcell members, they would be referred to as ALPINE-1 and ALPINE-2.

ALPINE and ALTITUDE only know how to reach ALASTAIR, but they are aware of at least some of other team members' identity should ALASTAIR be unavailable, and they would accept a message from ALBERT. Most often, the identity (and location) of the radio operator may not be shared. ALPINE and ALTITUDE, however, do not know one another. They do not know any of the members of team ALICE.

The legitimacy of the subcell structure came from the recruitment process, originally by the case officer and then by the cell leaders. Sometimes, the cell leader would propose subcell member names to the case officer, so the case officer could have a headquarters name check run before bringing the individual into the subcell. In principle, however, the subcell members would know ALPINE, and sometimes the other members of the ALPINE cell if they needed to work together; if ALPINE-1 and ALPINE-2 had independent assignments, they might not know each other. ALPINE-1 and ALPINE-2 certainly would not know ALASTAIR or anyone in the ALTITUDE or ALLOVER cells.
[[Image:Wnoc-Cell-1.png|thumb|Clandestine teams have built initial subcells]]

As the networks grow, a subcell leader might create his own cell, so ALPINE-2 might become the leader of the ALIMONY cell.

===Fault-tolerant cellular structures===
Modern communications theory has introduced methods to increase fault tolerance in cell organizations. In the past, if cell members only knew the cell leader, and the leader was neutralized, the cell was cut off from the rest of the organization. Game theory and graph theory have been applied to the study of optimal covert network design (see Lindelauf, R.H.A. et al. 2009. The influence of secrecy on the communication structure of covert networks. Social Networks 31: 126-137).

If a traditional cell had independent communications with the foreign support organization, headquarters might be able to arrange its reconnection. Another method is to have impersonal communications "side links" between cells, such as a pair of [[dead drop]]s, one for Team ALAN to leave "lost contact" messages to be retrieved by Team ALICE, and another dead drop for Team ALICE to leave messages for Team ALAN.

These links, to be used only on losing contact, do not guarantee a contact. When a team finds a message in its emergency drop, it might do no more than send an alert message to headquarters. Headquarters might determine, through [[SIGINT]] or other sources, that the enemy had captured the leadership and the entire team, and order the other team not to attempt contact. If headquarters can have reasonable confidence that there is a communications failure or partial compromise, it might send a new contact to the survivors.

When the cut-off team has electronic communications, such as the Internet, it has a much better chance of eluding surveillance and getting emergency instructions than by using a dead drop that can be under physical surveillance.

==Non-traditional models, exemplified by al-Qaeda==
Due to cultural differences, assuming the ''al-Qaeda Training Manual''&lt;ref name=AQTM&gt;{{cite web
 | url = https://fas.org/irp/world/para/aqmanual.pdf
 |format=PDF| title = al-Qaeda training manual
 | publisher = US Southern District Court, US New York City Attorney's Office, entered as evidence in Africa embassy bombings
}}&lt;/ref&gt; is authentic, eastern cell structures may differ from the Western mode. "Al-Qaida's minimal core group, only accounting for the leadership, can also be viewed topologically as a ring or chain network, with each leader/node heading their own particular hierarchy.

"Such networks function by having their sub-networks provide information and other forms of support (the ‘many-to-one’ model), while the core group supplies ‘truth’ and decisions/directions (the ‘one-to-many’ model). Trust and personal relationships are an essential part of the Al-Qaida network (a limiting factor, even while it provides enhanced security). Even while cell members are trained as ‘replaceable’ units, ‘vetting’ of members occurs during the invited training period under the observation of the core group.&lt;ref name=Sleepers&gt;{{cite web
 | url = http://www.metatempo.com/huntingthesleepers.pdf
 |format=PDF| title = Hunting the Sleepers: Tracking al-Qaida's Covert Operatives
 | date = 2001-12-31
 | author = Decision Support Systems, Inc.
 | accessdate = 2007-11-17
}}&lt;/ref&gt;

Cells of this structure are built outwards, from an internal leadership core. Superficially, this might be likened to a Western cell structure that emanates from a headquarters, but the Western centrality is bureaucratic, while structures in other non-western cultures builds on close personal relationships, often built over years, perhaps involving family or other in-group linkages. Such in-groups are thus extremely hard to infiltrate; infiltration has a serious chance only outside the in-group. Still, it may be possible for an in-group to be compromised through [[COMINT]] or, in rare cases, by compromising a member.

The core group is logically a ring, but is superimposed on an inner hub-and-spoke structure of ideological authority. Each member of the core forms another hub and spoke system (see [[#Infrastructure cells|infrastructure cells]]), the spokes leading to infrastructure cells under the supervision of the core group member, and possibly to operational groups which the headquarters support. Note that in this organization, there is a point at which the operational cell becomes autonomous of the core. Members surviving the operation may rejoin at various points.
[[Image:T-Cell-0.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

Osama, in this model, has the main responsibility of commanding the organization and being the spokesman on propaganda video and audio messages distributed by the propaganda cell. The other members of the core each command one or more infrastructure cells.

While the tight coupling enhances security, it can limit flexibility and the ability to scale the organization. This in-group, while sharing tight cultural and ideological values, is not committed to a bureaucratic process.

"Members of the core group are under what could be termed 'positive control'—long relationships
and similar mindsets make 'control' not so much of an issue, but there are distinct roles, and position (structural, financial, spiritual) determines authority, thus making the core group a hierarchy topologically.&lt;ref name=Sleepers /&gt;

In the first example of the core, each member knows how to reach two other members, and also knows the member(s) he considers his ideological superior. Solid lines show basic communication, dotted red arrows show the first level of ideological respect, and dotted blue arrows show a second level of ideological respect.

If Osama, the most respected, died, the core would reconstitute itself. While different members have an individual ideological guide, and these are not the same for all members, the core would reconstitute itself with Richard as most respected.

Assume there are no losses, and Osama can be reached directly only by members of the core group. Members of outer cells and support systems might know him only as "the Commander", or, as in the actual case of al-Qaeda, Osama bin Laden's face is recognizable worldwide, but only a few people know where he was or even how to contact him.

===Infrastructure cells===
Any clandestine or covert service, especially a non-national one, needs a variety of technical and administrative functions. Some of these services include:&lt;ref name=Sleepers /&gt;

# Forged documents and counterfeit currency
# Apartments and hiding places
# Communication means
# Transportation means
# Information
# Arms and ammunition
# Transport

Other functions include psychological operations, training, and finance.

A national intelligence service&lt;ref name=CIAsupport&gt;{{cite web
 | url = https://www.cia.gov/offices-of-cia/mission-support/who-we-are.html
 | author = US Central Intelligence Agency
 | title = Support to Mission: Who We Are
 | accessdate = 2007-11-19
}}&lt;/ref&gt;
has a support organization to deal with services such as finance, logistics, facilities (e.g., [[#Safehouses and Other Meeting Places|safehouses]]), information technology, communications, training, weapons and explosives, medical services, etc. Transportation alone is a huge function, including the need to buy tickets without drawing suspicion, and, where appropriate, using private vehicles. Finance includes the need to transfer money without coming under the suspicion of financial security organizations.

Some of these functions, such as finance, are far harder to operate in remote areas, such as the [[FATA]] of [[Pakistan]], than in cities with large numbers of official and unofficial financial institutions, and the communications to support them. If the financial office is distant from the remote headquarters, there is a need for [[couriers]], who must be trusted to some extent, but they may not know the contents of their messages or the actual identity of sender and/or receiver. The couriers, depending on the balance among type and size of message, security, and technology available, may memorize messages, carry audio or video recordings, or hand-carry computer media.
[[Image:T-Cell-1.png|thumb|Core group and infrastructure cells; military cells in training]]

"These cells are socially embedded (less so than the core group, however), structurally embedded, functionally embedded (they are specialized into a domain), and knowledge base-specific (there does not seem to be a great deal of cross-training, or lateral mobility in the organization). Such cells are probably subjected to a mixture of positive and negative control ("do this, do these sorts of things, don’t do that")."&lt;ref name=Sleepers /&gt;

{| class="wikitable"
&lt;caption&gt;Core Structure of Non-National Group&lt;/caption&gt;
|-
! Member
! Infrastructure commanded
|-
| Richard
| Finance
|-
| Anton
| Military training/operations 1
|-
| Hassan
| Military training/operations 2
|-
| David
| Transportation
|-
| Kim
| Communications and propaganda
|}

The leaders of military cells are responsible for training them, and, when an operation is scheduled, selecting the operational commander, giving him the basic objective and arranging whatever support is needed, and then release him from tight control to execute the meeting. Depending on the specific case, the military leaders might have direct, possibly one-way, communications with their cells, or they might have to give Kim the messages to be transmitted, by means that Anton and Hassan have no need to know.

Note that Anton does not have a direct connection to Kim. Under normal circumstances, he sacrifices efficiency for security, by passing communications requests through Hassan. The security structure also means that Hassan does not know the members of Anton's cells, and Kim may know only ways to communicate with them but not their identity.

Kim operates two systems of cells, one for secure communications and one for propaganda. To send out a propaganda message, Osama must pass it to Kim. If Kim were compromised, the core group might have significant problems with any sort of outside communications.

Terrorist networks do not match cleanly to other cell systems that regularly report to a headquarters. The apparent al-Qaeda methodology of letting operational cells decide on their final dates and means of attack exhibit an operational pattern, but not a periodicity that could easily be used for an [[Intelligence analysis management#Indications &amp; warning checklists|indications checklist]] appropriate for a warning center. Such lists depend on seeing a local pattern to give a specific warning.&lt;ref name=Vos&gt;{{cite web
 | title = Modeling Terrorist Networks - Complex Systems at the Mid-Range
 | first1 = Philip Vos
 | last1 = Fellman
 | first2 = Roxana
 | last2 = Wright
 | url = http://www.psych.lse.ac.uk/complexity/Conference/FellmanWright.pdf
 |format=PDF| accessdate = 2007-11-02
}}&lt;/ref&gt;

Note that Hassan has two subordinates that have not yet established operational cells. These subordinates can be considered '''sleepers''', but not necessarily with a sleeper cell.

===Operational cells===
For each mission are created one or more operational cells. If the al-Qaeda signature of multiple concurrent attacks is used, there may be an operational cell for each target location. It will depend on the operation if they will need any support cells in the operational area. For example, it may be more secure to have a local cell build bombs, which will be delivered by cells coming from outside the area.

"Operational cells are not created, but instead 'seeded' utilizing individuals spotted or that request assistance (both groups are 'vetted' by being trained under the observation of the core group, which dramatically restricts the opportunity for passing off walk-ins under false flag). Categorization of operational cells appears to be by capabilities, region, and then task/operation. Operational cells are composed of members whose worldview has been firmly tested—necessary to front-load, because such cells are dispersed back to their own local control (or negative control—proscribed behavior—with positive control only coming in the form of contact for synchronization or support)."&lt;ref name=Sleepers /&gt;

If operational cells routinely are "released" ''curved dotted lines on link to military cells'' to select their final operational parameters, they use a different paradigm than governmental clandestine or covert operations. On a number of cases, US special operations forces had to wait for Presidential authorization to make an attack, or even move to staging areas. Admittedly, a country would have to face the consequences of an inappropriate attack, so it may tend to be overcautious, where a terror network would merely shrug at the world being upset. Assuming that the al-Qaeda operational technique is not to use positive control, their operations may be more random, but also more unpredictable for counterterror forces. If their cells truly need constant control, there are communications links that might be detected by SIGINT, and if their command can be disrupted, the field units could not function. Since there is fairly little downside for terrorists to attack out of synchronization with other activities, the lack of positive control becomes a strength of their approach to cell organization.
[[Image:T-Cell-2.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

The operational cells need to have continuous internal communication; there is a commander, who may be in touch with infrastructure cells or, less likely from a security standpoint with the core group.

Al-Qaeda's approach, which even differs from that of earlier terrorist organizations, may be very viable for their goals:

* Cells are redundant and distributed, making them difficult to ‘roll up’
* Cells are coordinated, not under "command &amp; control"—this autonomy and local control makes them flexible, and enhances security
* Trust and comcon internally to the cell provide redundancy of potential command (a failure of Palestinian operations in the past), and well as a shared knowledgebase (which may mean, over time, that ‘cross training’ emerges inside a cell, providing redundancy of most critical skills and knowledge).&lt;ref name=Sleepers /&gt;

===Indirect support networks===
In the above graphic, note the indirect support network controlled by Richard's subcell.

"While Al-Qaida has elements of the organization designed to support the structure, but such elements are insufficient in meeting the needs of such an organization, and for security reasons there would be redundant and secondary-/tertiary-networks that are unaware of their connection to Al-Qaida. These networks, primarily related to fundraising and financial activities, as well as technology providers, are in a ‘use’ relationship with Al-Qaida—managed through cut-outs or individuals that do not inform them of the nature of activities, and that may have a cover pretext sufficient to deflect questions or inquiry."&lt;ref name=Sleepers /&gt;

===A possible countermeasure===
In 2002, ''U.S. News &amp; World Report'' said that American intelligence is beginning to acquire a sufficiently critical mass of intelligence on al-Qaida indicating, "Once thought nearly impossible to penetrate, al Qaeda is proving no tougher a target than the KGB or the Mafia--closed societies that took the U.S. government years to get inside. "We're getting names, the different camps they trained at, the hierarchy, the infighting," says an intelligence official. "It's very promising."&lt;ref name=Kaplan2002&gt;{{Cite journal
 | title = Run and Gun: Al Qaeda arrests and intelligence hauls bring new energy to the war on terrorism
 | first = David E. | last = Kaplan
 | date = 22 September 2002
 | journal = U.S. News &amp; World Report
 | url = http://www.usnews.com/usnews/news/articles/020930/archive_022824.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; The report also said that the collected data has allowed the recruiting of informants.

Writing in the U.S. Army journal ''Military Review'', David W. Pendall  suggested that a "catch-and-release program for suspected operatives might create reluctance or distrust in such suspects and prevent them from further acts or, perhaps more important, create distrust in the cell leaders of these individuals in the future." The author noted the press release describing Ramzi Binalshib's cooperation with the United States "are sure to prevent reentry into a terrorist cell as a trusted member and most likely limits the further trust and assignments of close cell associates still at large. The captor would determine when to name names and when to remain silent."&lt;ref name=Pendall2004&gt;{{Cite journal
 | date = January–February 2004
 | journal = Military Review
 | url = http://calldp.leavenworth.army.mil
 | first = David W. | last = Pendall
 | title =Effects-Based Operations and the Exercise of National Power
 | publisher = [[United States Army Combined Arms Center]]
 | postscript = &lt;!--None--&gt;
}}  Find the article by going through the Military Review directories&lt;/ref&gt; Indeed, once intelligence learns the name and characteristics of an at-large adversary, as well as some sensitive information that would plausibly be known to him, a news release could be issued to talk about his cooperation. Such a method could not be used too often, but, used carefully, could disturb the critical trust networks. The greatest uncertainty might be associated with throwing doubt onto a key member of an operational cell that has gone autonomous.

==See also==
* [[Leaderless resistance]]
* [[Lone wolf (terrorism)]]

==References==
{{reflist | 2}}

==External links==
* [http://theriskyshift.com/2012/06/an-introduction-to-terrorist-organisational-structures/ An Introduction To Terrorist Organisational Structures]

{{Intelligence cycle management}}

[[Category:Counter-intelligence]]
[[Category:Types of espionage]]
[[Category:Intelligence analysis]]
[[Category:Military intelligence]]
[[Category:Military tactics]]
[[Category:Secrecy]]
[[Category:Terrorism tactics]]

[[http:/www.cimacell.com/wiki/index.php?title=Structure|Reachback Ops]]</text>
    <sha1>2b500473b925e3ea87fa96669fa7cf002ee6fa22</sha1>
  </revision>
  <revision>
    <id>87</id>
    <parentid>86</parentid>
    <timestamp>2015-12-27T01:33:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39466" xml:space="preserve">{{for|the general use of a cellular structure by an organization, such as by a business|Cellular organization (disambiguation)}}
{{redirect|Sleeper cell}}
{{Use dmy dates|date=July 2011}}
{{multiple issues|
{{Essay-like|date=July 2011}}
{{POV|date=September 2012}}
{{Original research|date=January 2015}}
{{cleanup|reason=Poorly written, poorly referenced, marked essay-like (mostly user Hcberkowitz's edits; see page history) and POV issues and generally underlinked|date=January 2015}}
{{cleanup-rewrite|date=January 2015}}
{{Expert-subject|date=January 2015}}
}}

{{terrorism}}
A '''clandestine cell''' structure is a method for organizing a group of people like [[French resistance|resistance]] fighters or terrorists in such a way that it can more effectively resist penetration by an opposing organization (e.g., a law enforcement organization). In a cell structure, each small group of people in the cell only know the identities of the people in their cell; as such, if a cell member is apprehended and interrogated, he or she will not know the identities of the higher-ranking individuals in the organization. Depending on the group's [[philosophy]], its operational area, the communications technologies available, and the nature of the mission, it can range from a strict hierarchy to an extremely distributed organization. It is also a method used by [[organized crime|criminal organizations]], [[undercover]] operatives, and unconventional warfare (UW) units led by [[special forces]]. Historically, clandestine organizations have avoided electronic communications, because [[signals intelligence]] is a strength of conventional militaries and counterintelligence organizations.{{citation needed|date=August 2012}}

In the context of [[tradecraft]], [[covert operation|covert]] and [[clandestine operation|clandestine]] are not synonymous. As noted in the definition (which has been used by the United States and NATO since World War II) in a covert operation the identity of the sponsor is concealed, while in a clandestine operation the operation itself is concealed. Put differently, clandestine means "hidden", while covert means "deniable". The adversary is aware that a covert activity is happening, but does not know who is doing it, and certainly not their sponsorship. Clandestine activities, however, if successful, are completely unknown to the adversary, and their function, such as espionage, would be neutralized if there was any awareness of the activity.

A '''sleeper cell''' refers to a cell, or isolated grouping of [[sleeper agent]]s that lies dormant until it receives orders or decides to act.

==History==

=== Provisional Irish Republican Army===
As opposed to the [[French Resistance]], the modern [[Provisional Irish Republican Army]] (PIRA) has a history going back to Irish revolutionary forces in the early 20th century, but has little external control.  Its doctrine and organization have changed over time, given factors such as the independence of 26 of Ireland's 32 counties, the continued British control of Northern Ireland and the simple passage of time and changes in contemporary thinking and technology.&lt;ref name=Leahy&gt;{{cite web
 | url = http://cgsc.cdmhost.com/cgi-bin/showfile.exe?CISOROOT=/p4013coll2&amp;CISOPTR=386&amp;filename=387.pdf
 |format=PDF| author = Leahy, Kevin C.
 | year = 2005
 | title = The Impact of Technology on the Command, Control, and Organizational Structure of Insurgent Groups
 | accessdate=2007-12-04
}}&lt;/ref&gt;

Officially, the PIRA is hierarchical, but, especially as British security forces became more effective, changed to a semiautonomous model for its operational and certain of its support cells (e.g., transportation, intelligence, cover and security).&lt;ref name=GreenBook&gt;{{cite web
 | url = https://web.archive.org/web/20110606012137/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html
 | author = Irish Republican Army
 | title = The Green Book
 | accessdate=2007-12-04
|archiveurl=https://web.archive.org/web/20070616132240/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html|archivedate=2007-06-16}}&lt;/ref&gt; Its leadership sees itself as guiding and consensus-building. The lowest-level cells, typically of 2-5 people, tend to be built by people with an existing personal relationship. British counterinsurgents could fairly easily understand the command structure, but not the workings of the operational cells.

The IRA has an extensive network of inactive or sleeper cells, so new ''ad hoc'' organizations may appear for any specific operation.

===World War II French Resistance===
In World War II, [[Operation Jedburgh]] teams parachuted into occupied France to lead unconventional warfare units.&lt;ref name=Hall&gt;{{cite book
 | author = Hall, Roger
 | title = You're Stepping on my Cloak and Dagger
 | publisher = Bantam Books
 | year =1964
}}&lt;/ref&gt;&lt;ref name=SOETO&gt;{{cite book
 | chapterurl = http://www.history.army.mil/books/wwii/70-42/70-423.htm
 | chapter = Chapter 3: Special Operations in the European Theater
 | publisher = [[United States Army Center of Military History]]
| url = http://www.history.army.mil/books/wwii/70-42/70-42c.htm
| title = U.S. Army Special Operations in World War II
| first = David W.
| last = Hogan
| id = CMH Pub 70-42
|year = 1992
| location = Washington, D.C.
}}&lt;/ref&gt; They would be composed of two officers, one American or British, and the other French, the latter preferably from the area into which they landed. The third member of the team was a radio operator.

Especially through the French member, they would contact trusted individuals in the area of operation, and ask them to recruit a team of trusted subordinates (i.e., a subcell). If the team mission were sabotage, reconnaissance, or espionage, there was no need to meet in large units. If the team was to carry out direct action, often an unwise mission unless an appreciable number of the locals had military experience, it would be necessary to assemble into units for combat. Even then, the hideouts of the leadership were known only to subcell leaders. The legitimacy of the Jedburgh team came from its known affiliation with Allied powers, and it was a structure more appropriate for UW than for truly clandestine operations.

===National Front for the Liberation of South Vietnam===
Also known as the [[Viet Cong]], this organization grew from earlier anticolonial groups fighting the French, as well as anti-Japanese guerillas during World War II.&lt;ref name=VietCong&gt;{{cite book
 | author = Pike, Douglas
 | title = Viet Cong: Organization and Technique of the National Liberation Front of South Vietnam
 | publisher = MIT Press
 | year = 1970
}}&lt;/ref&gt;
Its command, control, and communication techniques derived from the experiences of these earlier insurgent groups. The group had extensive support from North Vietnam, and, indirectly, from the Soviet Union. It had parallel political and military structures, often overlapping. See [[Viet Cong and PAVN strategy and tactics]].
[[Image:Vcnvastructure4rev.jpg|thumb|right |A dual, but sometimes overlapping, Party and Military structure was top-down]]
The lowest level consisted of three-person cells who operated quite closely, and engaging in the sort of [[self-criticism]] common, as a bonding method, to Communist organizations.{{Citation needed|date=June 2014}}

==Parallel organizations==
The NLF and PIRA, as well as other movements, have chosen to have parallel political and military organizations. In the case of the NLF, other than some individuals with sanctuary in North Vietnam, the political organization could not be overt during the [[Vietnam War]]. After the war ended, surviving NLF officials held high office.

In the case of the PIRA, its political wing, [[Sinn Féin]], became increasingly overt, and then a full participant in politics. [[Hamas]] and [[Hezbollah]] also have variants of overt political/social service and covert military wings.

The overt political/social–covert military split avoided the inflexibility of a completely secret organization. Once an active insurgency began, the secrecy {{clarify span|could limit|date=January 2015}}&lt;!-- what? --&gt; freedom of action, distort information about goals and ideals, and restrict communication within the insurgency.&lt;ref name=FM3-24&gt;{{cite web
 | title = FM 3-24: Counterinsurgency
 | author = US Department of the Army
 |date=December 2006
 | url = https://fas.org/irp/doddir/army/fm3-24.pdf
|format=PDF}}&lt;/ref&gt; In a split organization, the public issues can be addressed overtly, while military actions were kept covert and intelligence functions stay clandestine.

==External support==
Many cell systems still receive, with due attention to security, support from the outside. This can range from leaders, trainers and supplies (such as the Jedburgh assistance to the French Resistance), or a safe haven for overt activities (such as the NLF spokesmen in Hanoi).

External support need not be overt. Certain Shi'a groups in Iraq, for example, do receive assistance from Iran{{Citation needed|date=March 2009}}, but this is not a public position of the government of Iran, and may even be limited to factions of that government.  Early US support to the Afghan Northern Alliance against the Taliban used clandestine operators from both the [[CIA]] and [[United States Army Special Forces]]. As the latter conflict escalated, the US participation became overt.

Note that both [[unconventional warfare]] (UW) (guerrilla operations) and [[foreign internal defense]] (FID) (counterinsurgency) may be covert and use cellular organization.

In a covert FID mission, only selected host nation (HN) leaders are aware of the foreign support organization. Under [[Operation White Star]], US personnel gave covert FID assistance to the Royal Lao Army starting in 1959, became overt in 1961, and ceased operations in 1962.

==Models of insurgency and associated cell characteristics==
While different kinds of insurgency differ in where they place clandestine or covert cells, when certain types of insurgency grow in power, the cell system is deemphasized. Cells still may be used for leadership security, but, if overt violence by organized units becomes significant, cells are less important. In Mao's three-stage doctrine,&lt;ref name=Mao1967&gt;{{cite book
 | title = On Protracted War
 | author = Mao,  Zedong | authorlink = Mao Zedong
 | year = 1967
 | publisher = Foreign Language Press, Beijing
}}&lt;/ref&gt; cells are still useful in Phase II to give cover to part-time guerillas, but, as the insurgency creates full-time military units in Phase III, the main units are the focus, not the cells. The [[Eighth Route Army]] did not run on a cell model.

When considering where cells exist with respect to the existing government, the type of insurgency needs to be considered. One US Army reference was Field Manual 100-20, which has been superseded by FM3-07.&lt;ref name=FM3-07&gt;{{cite web
 | title = FM 3-07 (formerly FM 100-20): Stability Operations and Support Operations
 | date = 20 February 2003
 | author = US Department of the Army
 | url = https://atiam.train.army.mil/soldierPortal/atia/adlsc/view/altfmt/9630-1
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; Drawing on this work, Nyberg (a [[United States Marine Corps]] officer) extended the ideas to describe four types of cell system, although his descriptions also encompass types of insurgencies that the cell system supports.&lt;ref name=Nyberg&gt;{{Cite journal
 | title = Insurgency: The Unsolved Mystery
 | first = Eric N. | last = Nyberg
 | publisher = US Marine Corps University Command and Staff College
 | year = 1991
 | url = http://www.globalsecurity.org/military/library/report/1991/NEN.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt;  At present, there is a new type associated with transnational terrorist insurgencies.

# Traditional: the slowest to form, this reflects a principally indigenous insurgency, initially with limited goals. It is more secure than others, as it tends to grow from people with social, cultural or family ties. The insurgents resent a government that has failed to recognize  tribal, racial, religious or linguistic groups "who perceive that the government has denied their rights and interests and work to establish or restore them. They seldom seek to overthrow the government or control the whole society; however, they frequently attempt to withdraw from government control through autonomy or semiautonomy." The Mujahideen in Afghanistan and the Kurdish revolt in Iraq illustrate the traditional pattern of insurgency. [[al-Qaeda]] generally operates in this mode, but if they become strong enough in a given area, they may change to the mass-oriented form.
# Subversive: Usually driven by an organization that contains at least some of the governing elite, some being sympathizers already in place, and others who penetrate the government. When they use violence, it has a specific purpose, such as coercing voters, intimidating officials, and disrupting and discrediting the government. Typically, there is a political arm (such as  [[Sinn Féin]] or the [[Viet Cong|National Liberation Front]]) that directs the military in planning carefully coordinated violence. "Employment of violence is designed to show the system to be incompetent and to provoke the government to an excessively violent response which further undermines its legitimacy." The [[Nazi]] rise to power, in the 1930s, is another example of subversion. Nazi members of parliament and street fighters were hardly clandestine, but the overall plan of the Nazi leadership to gain control of the nation was hidden. "A subversive insurgency is suited to a more permissive political environment which allows the insurgents to use both legal and illegal methods to accomplish their goals. Effective government resistance may convert this to a critical-cell model.
# Critical-cell: Critical cell is useful when the political climate becomes less permissive than one that allowed shadow cells. While other cell types try to form intelligence cells within the government, this type sets up "[[Continuity of government|shadow government]]" cells that can seize power once the system is destroyed both by external means and the internal subversion. This model fits the classic [[coup d'etat]],&lt;ref name=Luttwak&gt;{{cite book
 | title = Coup d'etat: A Practical Handbook
 | year = 1968
 | author = Luttwak, Edward | authorlink = Edward Luttwak
 | publisher = Harvard University Press
}}&lt;/ref&gt; and often tries to minimize violence. Variants include the [[Sandinista]] takeover of an existing government weakened by external popular revolution. "Insurgents also seek to infiltrate the government's institutions, but their object is to destroy the system from within." Clandestine cells form inside the government. "The use of violence remains covert until the government is so weakened that the insurgency's superior organization seizes power, supported by the armed force. One variation of this pattern is when the insurgent leadership permits the popular revolution to destroy the existing government, then emerges to direct the formation of a new government. Another variation is seen in the [[Cuba]]n revolution&lt;ref name=Guevara&gt;{{cite book
 | author = Guevara, Ernesto "Che"
 | title = On Guerilla Warfare
 | publisher = Praeger
 | year = 1961
}}&lt;/ref&gt; and is referred to as the foco (or Cuban model) insurgency. This model involves a single, armed cell which emerges in the midst of degenerating government legitimacy and becomes the nucleus around which mass popular support rallies.  The insurgents use this support to establish control and erect new institutions."
# Mass-oriented: where the subversive and covert-cell systems work from within the government, the mass-oriented builds a government completely outside the existing one, with the intention of replacing it. Such "insurgents patiently construct a base of passive and active political supporters, while simultaneously building a large armed element of guerrilla and regular forces.  They plan a protracted campaign of increasing violence to destroy the government and its institutions from the outside.  They have a well-developed ideology and carefully determine their objectives.  They are highly organized and effectively use propaganda and guerrilla action to mobilize forces for a direct political and military challenge to the government." The revolution that produced the [[Peoples' Republic of China]], the [[American Revolution]], and the [[Shining Path]] insurgency in Peru are examples of the mass-oriented model. Once established, this type of insurgency is extremely difficult to defeat because of its great depth of organization.

==Classic models for cell system operations==
Different kinds of cell organizations have been used for different purposes. This section focuses on clandestine cells, as would be used for [[espionage]], [[sabotage]], or the organization for [[unconventional warfare]]. When unconventional warfare starts using overt units, the cell system tends to be used only for sensitive leadership and intelligence roles.&lt;ref name=Mao1967 /&gt; The examples here will use [[CIA cryptonym]]s as a naming convention used to identify members of the cell system. Cryptonyms begin with a two-letter country or subject name (e.g., AL), followed with an arbitrary word. It is considered elegant to have the code merge with the other letters to form a pronounceable word.

===Operations under official cover===
Station BERRY operates, for country B, in target country BE. It has three case officers and several support officers. Espionage operation run by case officers under diplomatic cover, they would have to with the basic recruiting methods described in this article. Case officer BETTY runs the local agents BEN and BEATLE. Case officer BESSIE runs BENSON and BEAGLE.
[[Image:Wdip-Cell-0.png|thumb|Representative diplomatic-cover station and networks]]

Some recruits, due to the sensitivity of their position or their personalities not being appropriate for cell leadership, might not enter cells but be run as singletons, perhaps by other than the recruiting case officer. Asset BARD is a different sort of highly sensitive singleton, who is a joint asset of the country B, and the country identified by prefix AR. ARNOLD is a case officer from the country AR embassy, who knows only the case officer BERTRAM and the security officer BEST. ARNOLD does not know the station chief of BERRY or any of its other personnel. Other than BELL and BEST, the Station personnel only know BERTRAM as someone authorized to be in the Station, and who is known for his piano playing at embassy parties. He is covered as Cultural Attache, in a country that has very few pianos. Only the personnel involved with BARD know that ARNOLD is other than another friendly diplomat.

In contrast, BESSIE and BETTY know one another, and procedures exist for their taking over each other's assets in the event one of the two is disabled.

Some recruits, however, would be qualified to recruit their own subcell, as BEATLE has done. BESSIE knows the identity of BEATLE-1 and BEATLE-2, since he had them checked by headquarters counterintelligence before they were recruited. Note that a cryptonym does not imply anything about its  designee, such as gender.

===Clandestine presence===
The diagram of "initial team presence" shows that two teams, ALAN and ALICE, have successfully entered an area of operation, the country coded AL, but are only aware of a pool of potential recruits, and have not yet actually recruited anyone. They communicate with one another only through headquarters, so compromise of one team will not affect the other.
[[Image:Wnoc-Cell-0.png|thumb|left |Initial team presence by 2 separate clandestine teams with no official cover]]

Assume that in team ALAN, ALASTAIR is one of the officers with local contacts, might recruit two cell leaders, ALPINE and ALTITUDE. The other local officer in the team, ALBERT, recruits ALLOVER.  When ALPINE recruited two subcell members, they would be referred to as ALPINE-1 and ALPINE-2.

ALPINE and ALTITUDE only know how to reach ALASTAIR, but they are aware of at least some of other team members' identity should ALASTAIR be unavailable, and they would accept a message from ALBERT. Most often, the identity (and location) of the radio operator may not be shared. ALPINE and ALTITUDE, however, do not know one another. They do not know any of the members of team ALICE.

The legitimacy of the subcell structure came from the recruitment process, originally by the case officer and then by the cell leaders. Sometimes, the cell leader would propose subcell member names to the case officer, so the case officer could have a headquarters name check run before bringing the individual into the subcell. In principle, however, the subcell members would know ALPINE, and sometimes the other members of the ALPINE cell if they needed to work together; if ALPINE-1 and ALPINE-2 had independent assignments, they might not know each other. ALPINE-1 and ALPINE-2 certainly would not know ALASTAIR or anyone in the ALTITUDE or ALLOVER cells.
[[Image:Wnoc-Cell-1.png|thumb|Clandestine teams have built initial subcells]]

As the networks grow, a subcell leader might create his own cell, so ALPINE-2 might become the leader of the ALIMONY cell.

===Fault-tolerant cellular structures===
Modern communications theory has introduced methods to increase fault tolerance in cell organizations. In the past, if cell members only knew the cell leader, and the leader was neutralized, the cell was cut off from the rest of the organization. Game theory and graph theory have been applied to the study of optimal covert network design (see Lindelauf, R.H.A. et al. 2009. The influence of secrecy on the communication structure of covert networks. Social Networks 31: 126-137).

If a traditional cell had independent communications with the foreign support organization, headquarters might be able to arrange its reconnection. Another method is to have impersonal communications "side links" between cells, such as a pair of [[dead drop]]s, one for Team ALAN to leave "lost contact" messages to be retrieved by Team ALICE, and another dead drop for Team ALICE to leave messages for Team ALAN.

These links, to be used only on losing contact, do not guarantee a contact. When a team finds a message in its emergency drop, it might do no more than send an alert message to headquarters. Headquarters might determine, through [[SIGINT]] or other sources, that the enemy had captured the leadership and the entire team, and order the other team not to attempt contact. If headquarters can have reasonable confidence that there is a communications failure or partial compromise, it might send a new contact to the survivors.

When the cut-off team has electronic communications, such as the Internet, it has a much better chance of eluding surveillance and getting emergency instructions than by using a dead drop that can be under physical surveillance.

==Non-traditional models, exemplified by al-Qaeda==
Due to cultural differences, assuming the ''al-Qaeda Training Manual''&lt;ref name=AQTM&gt;{{cite web
 | url = https://fas.org/irp/world/para/aqmanual.pdf
 |format=PDF| title = al-Qaeda training manual
 | publisher = US Southern District Court, US New York City Attorney's Office, entered as evidence in Africa embassy bombings
}}&lt;/ref&gt; is authentic, eastern cell structures may differ from the Western mode. "Al-Qaida's minimal core group, only accounting for the leadership, can also be viewed topologically as a ring or chain network, with each leader/node heading their own particular hierarchy.

"Such networks function by having their sub-networks provide information and other forms of support (the ‘many-to-one’ model), while the core group supplies ‘truth’ and decisions/directions (the ‘one-to-many’ model). Trust and personal relationships are an essential part of the Al-Qaida network (a limiting factor, even while it provides enhanced security). Even while cell members are trained as ‘replaceable’ units, ‘vetting’ of members occurs during the invited training period under the observation of the core group.&lt;ref name=Sleepers&gt;{{cite web
 | url = http://www.metatempo.com/huntingthesleepers.pdf
 |format=PDF| title = Hunting the Sleepers: Tracking al-Qaida's Covert Operatives
 | date = 2001-12-31
 | author = Decision Support Systems, Inc.
 | accessdate = 2007-11-17
}}&lt;/ref&gt;

Cells of this structure are built outwards, from an internal leadership core. Superficially, this might be likened to a Western cell structure that emanates from a headquarters, but the Western centrality is bureaucratic, while structures in other non-western cultures builds on close personal relationships, often built over years, perhaps involving family or other in-group linkages. Such in-groups are thus extremely hard to infiltrate; infiltration has a serious chance only outside the in-group. Still, it may be possible for an in-group to be compromised through [[COMINT]] or, in rare cases, by compromising a member.

The core group is logically a ring, but is superimposed on an inner hub-and-spoke structure of ideological authority. Each member of the core forms another hub and spoke system (see [[#Infrastructure cells|infrastructure cells]]), the spokes leading to infrastructure cells under the supervision of the core group member, and possibly to operational groups which the headquarters support. Note that in this organization, there is a point at which the operational cell becomes autonomous of the core. Members surviving the operation may rejoin at various points.
[[Image:T-Cell-0.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

Osama, in this model, has the main responsibility of commanding the organization and being the spokesman on propaganda video and audio messages distributed by the propaganda cell. The other members of the core each command one or more infrastructure cells.

While the tight coupling enhances security, it can limit flexibility and the ability to scale the organization. This in-group, while sharing tight cultural and ideological values, is not committed to a bureaucratic process.

"Members of the core group are under what could be termed 'positive control'—long relationships
and similar mindsets make 'control' not so much of an issue, but there are distinct roles, and position (structural, financial, spiritual) determines authority, thus making the core group a hierarchy topologically.&lt;ref name=Sleepers /&gt;

In the first example of the core, each member knows how to reach two other members, and also knows the member(s) he considers his ideological superior. Solid lines show basic communication, dotted red arrows show the first level of ideological respect, and dotted blue arrows show a second level of ideological respect.

If Osama, the most respected, died, the core would reconstitute itself. While different members have an individual ideological guide, and these are not the same for all members, the core would reconstitute itself with Richard as most respected.

Assume there are no losses, and Osama can be reached directly only by members of the core group. Members of outer cells and support systems might know him only as "the Commander", or, as in the actual case of al-Qaeda, Osama bin Laden's face is recognizable worldwide, but only a few people know where he was or even how to contact him.

===Infrastructure cells===
Any clandestine or covert service, especially a non-national one, needs a variety of technical and administrative functions. Some of these services include:&lt;ref name=Sleepers /&gt;

# Forged documents and counterfeit currency
# Apartments and hiding places
# Communication means
# Transportation means
# Information
# Arms and ammunition
# Transport

Other functions include psychological operations, training, and finance.

A national intelligence service&lt;ref name=CIAsupport&gt;{{cite web
 | url = https://www.cia.gov/offices-of-cia/mission-support/who-we-are.html
 | author = US Central Intelligence Agency
 | title = Support to Mission: Who We Are
 | accessdate = 2007-11-19
}}&lt;/ref&gt;
has a support organization to deal with services such as finance, logistics, facilities (e.g., [[#Safehouses and Other Meeting Places|safehouses]]), information technology, communications, training, weapons and explosives, medical services, etc. Transportation alone is a huge function, including the need to buy tickets without drawing suspicion, and, where appropriate, using private vehicles. Finance includes the need to transfer money without coming under the suspicion of financial security organizations.

Some of these functions, such as finance, are far harder to operate in remote areas, such as the [[FATA]] of [[Pakistan]], than in cities with large numbers of official and unofficial financial institutions, and the communications to support them. If the financial office is distant from the remote headquarters, there is a need for [[couriers]], who must be trusted to some extent, but they may not know the contents of their messages or the actual identity of sender and/or receiver. The couriers, depending on the balance among type and size of message, security, and technology available, may memorize messages, carry audio or video recordings, or hand-carry computer media.
[[Image:T-Cell-1.png|thumb|Core group and infrastructure cells; military cells in training]]

"These cells are socially embedded (less so than the core group, however), structurally embedded, functionally embedded (they are specialized into a domain), and knowledge base-specific (there does not seem to be a great deal of cross-training, or lateral mobility in the organization). Such cells are probably subjected to a mixture of positive and negative control ("do this, do these sorts of things, don’t do that")."&lt;ref name=Sleepers /&gt;

{| class="wikitable"
&lt;caption&gt;Core Structure of Non-National Group&lt;/caption&gt;
|-
! Member
! Infrastructure commanded
|-
| Richard
| Finance
|-
| Anton
| Military training/operations 1
|-
| Hassan
| Military training/operations 2
|-
| David
| Transportation
|-
| Kim
| Communications and propaganda
|}

The leaders of military cells are responsible for training them, and, when an operation is scheduled, selecting the operational commander, giving him the basic objective and arranging whatever support is needed, and then release him from tight control to execute the meeting. Depending on the specific case, the military leaders might have direct, possibly one-way, communications with their cells, or they might have to give Kim the messages to be transmitted, by means that Anton and Hassan have no need to know.

Note that Anton does not have a direct connection to Kim. Under normal circumstances, he sacrifices efficiency for security, by passing communications requests through Hassan. The security structure also means that Hassan does not know the members of Anton's cells, and Kim may know only ways to communicate with them but not their identity.

Kim operates two systems of cells, one for secure communications and one for propaganda. To send out a propaganda message, Osama must pass it to Kim. If Kim were compromised, the core group might have significant problems with any sort of outside communications.

Terrorist networks do not match cleanly to other cell systems that regularly report to a headquarters. The apparent al-Qaeda methodology of letting operational cells decide on their final dates and means of attack exhibit an operational pattern, but not a periodicity that could easily be used for an [[Intelligence analysis management#Indications &amp; warning checklists|indications checklist]] appropriate for a warning center. Such lists depend on seeing a local pattern to give a specific warning.&lt;ref name=Vos&gt;{{cite web
 | title = Modeling Terrorist Networks - Complex Systems at the Mid-Range
 | first1 = Philip Vos
 | last1 = Fellman
 | first2 = Roxana
 | last2 = Wright
 | url = http://www.psych.lse.ac.uk/complexity/Conference/FellmanWright.pdf
 |format=PDF| accessdate = 2007-11-02
}}&lt;/ref&gt;

Note that Hassan has two subordinates that have not yet established operational cells. These subordinates can be considered '''sleepers''', but not necessarily with a sleeper cell.

===Operational cells===
For each mission are created one or more operational cells. If the al-Qaeda signature of multiple concurrent attacks is used, there may be an operational cell for each target location. It will depend on the operation if they will need any support cells in the operational area. For example, it may be more secure to have a local cell build bombs, which will be delivered by cells coming from outside the area.

"Operational cells are not created, but instead 'seeded' utilizing individuals spotted or that request assistance (both groups are 'vetted' by being trained under the observation of the core group, which dramatically restricts the opportunity for passing off walk-ins under false flag). Categorization of operational cells appears to be by capabilities, region, and then task/operation. Operational cells are composed of members whose worldview has been firmly tested—necessary to front-load, because such cells are dispersed back to their own local control (or negative control—proscribed behavior—with positive control only coming in the form of contact for synchronization or support)."&lt;ref name=Sleepers /&gt;

If operational cells routinely are "released" ''curved dotted lines on link to military cells'' to select their final operational parameters, they use a different paradigm than governmental clandestine or covert operations. On a number of cases, US special operations forces had to wait for Presidential authorization to make an attack, or even move to staging areas. Admittedly, a country would have to face the consequences of an inappropriate attack, so it may tend to be overcautious, where a terror network would merely shrug at the world being upset. Assuming that the al-Qaeda operational technique is not to use positive control, their operations may be more random, but also more unpredictable for counterterror forces. If their cells truly need constant control, there are communications links that might be detected by SIGINT, and if their command can be disrupted, the field units could not function. Since there is fairly little downside for terrorists to attack out of synchronization with other activities, the lack of positive control becomes a strength of their approach to cell organization.
[[Image:T-Cell-2.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

The operational cells need to have continuous internal communication; there is a commander, who may be in touch with infrastructure cells or, less likely from a security standpoint with the core group.

Al-Qaeda's approach, which even differs from that of earlier terrorist organizations, may be very viable for their goals:

* Cells are redundant and distributed, making them difficult to ‘roll up’
* Cells are coordinated, not under "command &amp; control"—this autonomy and local control makes them flexible, and enhances security
* Trust and comcon internally to the cell provide redundancy of potential command (a failure of Palestinian operations in the past), and well as a shared knowledgebase (which may mean, over time, that ‘cross training’ emerges inside a cell, providing redundancy of most critical skills and knowledge).&lt;ref name=Sleepers /&gt;

===Indirect support networks===
In the above graphic, note the indirect support network controlled by Richard's subcell.

"While Al-Qaida has elements of the organization designed to support the structure, but such elements are insufficient in meeting the needs of such an organization, and for security reasons there would be redundant and secondary-/tertiary-networks that are unaware of their connection to Al-Qaida. These networks, primarily related to fundraising and financial activities, as well as technology providers, are in a ‘use’ relationship with Al-Qaida—managed through cut-outs or individuals that do not inform them of the nature of activities, and that may have a cover pretext sufficient to deflect questions or inquiry."&lt;ref name=Sleepers /&gt;

===A possible countermeasure===
In 2002, ''U.S. News &amp; World Report'' said that American intelligence is beginning to acquire a sufficiently critical mass of intelligence on al-Qaida indicating, "Once thought nearly impossible to penetrate, al Qaeda is proving no tougher a target than the KGB or the Mafia--closed societies that took the U.S. government years to get inside. "We're getting names, the different camps they trained at, the hierarchy, the infighting," says an intelligence official. "It's very promising."&lt;ref name=Kaplan2002&gt;{{Cite journal
 | title = Run and Gun: Al Qaeda arrests and intelligence hauls bring new energy to the war on terrorism
 | first = David E. | last = Kaplan
 | date = 22 September 2002
 | journal = U.S. News &amp; World Report
 | url = http://www.usnews.com/usnews/news/articles/020930/archive_022824.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; The report also said that the collected data has allowed the recruiting of informants.

Writing in the U.S. Army journal ''Military Review'', David W. Pendall  suggested that a "catch-and-release program for suspected operatives might create reluctance or distrust in such suspects and prevent them from further acts or, perhaps more important, create distrust in the cell leaders of these individuals in the future." The author noted the press release describing Ramzi Binalshib's cooperation with the United States "are sure to prevent reentry into a terrorist cell as a trusted member and most likely limits the further trust and assignments of close cell associates still at large. The captor would determine when to name names and when to remain silent."&lt;ref name=Pendall2004&gt;{{Cite journal
 | date = January–February 2004
 | journal = Military Review
 | url = http://calldp.leavenworth.army.mil
 | first = David W. | last = Pendall
 | title =Effects-Based Operations and the Exercise of National Power
 | publisher = [[United States Army Combined Arms Center]]
 | postscript = &lt;!--None--&gt;
}}  Find the article by going through the Military Review directories&lt;/ref&gt; Indeed, once intelligence learns the name and characteristics of an at-large adversary, as well as some sensitive information that would plausibly be known to him, a news release could be issued to talk about his cooperation. Such a method could not be used too often, but, used carefully, could disturb the critical trust networks. The greatest uncertainty might be associated with throwing doubt onto a key member of an operational cell that has gone autonomous.

==See also==
* [[Leaderless resistance]]
* [[Lone wolf (terrorism)]]

==References==
{{reflist | 2}}

==External links==
* [http://theriskyshift.com/2012/06/an-introduction-to-terrorist-organisational-structures/ An Introduction To Terrorist Organisational Structures]

{{Intelligence cycle management}}

[[Category:Counter-intelligence]]
[[Category:Types of espionage]]
[[Category:Intelligence analysis]]
[[Category:Military intelligence]]
[[Category:Military tactics]]
[[Category:Secrecy]]
[[Category:Terrorism tactics]]

[http:/www.cimacell.com/wiki/index.php?title=Structure Reachback Ops]</text>
    <sha1>0d76002833887b7aaac78333dcb9c1d0708207a2</sha1>
  </revision>
  <revision>
    <id>88</id>
    <parentid>87</parentid>
    <timestamp>2015-12-27T01:34:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39467" xml:space="preserve">{{for|the general use of a cellular structure by an organization, such as by a business|Cellular organization (disambiguation)}}
{{redirect|Sleeper cell}}
{{Use dmy dates|date=July 2011}}
{{multiple issues|
{{Essay-like|date=July 2011}}
{{POV|date=September 2012}}
{{Original research|date=January 2015}}
{{cleanup|reason=Poorly written, poorly referenced, marked essay-like (mostly user Hcberkowitz's edits; see page history) and POV issues and generally underlinked|date=January 2015}}
{{cleanup-rewrite|date=January 2015}}
{{Expert-subject|date=January 2015}}
}}

{{terrorism}}
A '''clandestine cell''' structure is a method for organizing a group of people like [[French resistance|resistance]] fighters or terrorists in such a way that it can more effectively resist penetration by an opposing organization (e.g., a law enforcement organization). In a cell structure, each small group of people in the cell only know the identities of the people in their cell; as such, if a cell member is apprehended and interrogated, he or she will not know the identities of the higher-ranking individuals in the organization. Depending on the group's [[philosophy]], its operational area, the communications technologies available, and the nature of the mission, it can range from a strict hierarchy to an extremely distributed organization. It is also a method used by [[organized crime|criminal organizations]], [[undercover]] operatives, and unconventional warfare (UW) units led by [[special forces]]. Historically, clandestine organizations have avoided electronic communications, because [[signals intelligence]] is a strength of conventional militaries and counterintelligence organizations.{{citation needed|date=August 2012}}

In the context of [[tradecraft]], [[covert operation|covert]] and [[clandestine operation|clandestine]] are not synonymous. As noted in the definition (which has been used by the United States and NATO since World War II) in a covert operation the identity of the sponsor is concealed, while in a clandestine operation the operation itself is concealed. Put differently, clandestine means "hidden", while covert means "deniable". The adversary is aware that a covert activity is happening, but does not know who is doing it, and certainly not their sponsorship. Clandestine activities, however, if successful, are completely unknown to the adversary, and their function, such as espionage, would be neutralized if there was any awareness of the activity.

A '''sleeper cell''' refers to a cell, or isolated grouping of [[sleeper agent]]s that lies dormant until it receives orders or decides to act.

==History==

=== Provisional Irish Republican Army===
As opposed to the [[French Resistance]], the modern [[Provisional Irish Republican Army]] (PIRA) has a history going back to Irish revolutionary forces in the early 20th century, but has little external control.  Its doctrine and organization have changed over time, given factors such as the independence of 26 of Ireland's 32 counties, the continued British control of Northern Ireland and the simple passage of time and changes in contemporary thinking and technology.&lt;ref name=Leahy&gt;{{cite web
 | url = http://cgsc.cdmhost.com/cgi-bin/showfile.exe?CISOROOT=/p4013coll2&amp;CISOPTR=386&amp;filename=387.pdf
 |format=PDF| author = Leahy, Kevin C.
 | year = 2005
 | title = The Impact of Technology on the Command, Control, and Organizational Structure of Insurgent Groups
 | accessdate=2007-12-04
}}&lt;/ref&gt;

Officially, the PIRA is hierarchical, but, especially as British security forces became more effective, changed to a semiautonomous model for its operational and certain of its support cells (e.g., transportation, intelligence, cover and security).&lt;ref name=GreenBook&gt;{{cite web
 | url = https://web.archive.org/web/20110606012137/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html
 | author = Irish Republican Army
 | title = The Green Book
 | accessdate=2007-12-04
|archiveurl=https://web.archive.org/web/20070616132240/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html|archivedate=2007-06-16}}&lt;/ref&gt; Its leadership sees itself as guiding and consensus-building. The lowest-level cells, typically of 2-5 people, tend to be built by people with an existing personal relationship. British counterinsurgents could fairly easily understand the command structure, but not the workings of the operational cells.

The IRA has an extensive network of inactive or sleeper cells, so new ''ad hoc'' organizations may appear for any specific operation.

===World War II French Resistance===
In World War II, [[Operation Jedburgh]] teams parachuted into occupied France to lead unconventional warfare units.&lt;ref name=Hall&gt;{{cite book
 | author = Hall, Roger
 | title = You're Stepping on my Cloak and Dagger
 | publisher = Bantam Books
 | year =1964
}}&lt;/ref&gt;&lt;ref name=SOETO&gt;{{cite book
 | chapterurl = http://www.history.army.mil/books/wwii/70-42/70-423.htm
 | chapter = Chapter 3: Special Operations in the European Theater
 | publisher = [[United States Army Center of Military History]]
| url = http://www.history.army.mil/books/wwii/70-42/70-42c.htm
| title = U.S. Army Special Operations in World War II
| first = David W.
| last = Hogan
| id = CMH Pub 70-42
|year = 1992
| location = Washington, D.C.
}}&lt;/ref&gt; They would be composed of two officers, one American or British, and the other French, the latter preferably from the area into which they landed. The third member of the team was a radio operator.

Especially through the French member, they would contact trusted individuals in the area of operation, and ask them to recruit a team of trusted subordinates (i.e., a subcell). If the team mission were sabotage, reconnaissance, or espionage, there was no need to meet in large units. If the team was to carry out direct action, often an unwise mission unless an appreciable number of the locals had military experience, it would be necessary to assemble into units for combat. Even then, the hideouts of the leadership were known only to subcell leaders. The legitimacy of the Jedburgh team came from its known affiliation with Allied powers, and it was a structure more appropriate for UW than for truly clandestine operations.

===National Front for the Liberation of South Vietnam===
Also known as the [[Viet Cong]], this organization grew from earlier anticolonial groups fighting the French, as well as anti-Japanese guerillas during World War II.&lt;ref name=VietCong&gt;{{cite book
 | author = Pike, Douglas
 | title = Viet Cong: Organization and Technique of the National Liberation Front of South Vietnam
 | publisher = MIT Press
 | year = 1970
}}&lt;/ref&gt;
Its command, control, and communication techniques derived from the experiences of these earlier insurgent groups. The group had extensive support from North Vietnam, and, indirectly, from the Soviet Union. It had parallel political and military structures, often overlapping. See [[Viet Cong and PAVN strategy and tactics]].
[[Image:Vcnvastructure4rev.jpg|thumb|right |A dual, but sometimes overlapping, Party and Military structure was top-down]]
The lowest level consisted of three-person cells who operated quite closely, and engaging in the sort of [[self-criticism]] common, as a bonding method, to Communist organizations.{{Citation needed|date=June 2014}}

==Parallel organizations==
The NLF and PIRA, as well as other movements, have chosen to have parallel political and military organizations. In the case of the NLF, other than some individuals with sanctuary in North Vietnam, the political organization could not be overt during the [[Vietnam War]]. After the war ended, surviving NLF officials held high office.

In the case of the PIRA, its political wing, [[Sinn Féin]], became increasingly overt, and then a full participant in politics. [[Hamas]] and [[Hezbollah]] also have variants of overt political/social service and covert military wings.

The overt political/social–covert military split avoided the inflexibility of a completely secret organization. Once an active insurgency began, the secrecy {{clarify span|could limit|date=January 2015}}&lt;!-- what? --&gt; freedom of action, distort information about goals and ideals, and restrict communication within the insurgency.&lt;ref name=FM3-24&gt;{{cite web
 | title = FM 3-24: Counterinsurgency
 | author = US Department of the Army
 |date=December 2006
 | url = https://fas.org/irp/doddir/army/fm3-24.pdf
|format=PDF}}&lt;/ref&gt; In a split organization, the public issues can be addressed overtly, while military actions were kept covert and intelligence functions stay clandestine.

==External support==
Many cell systems still receive, with due attention to security, support from the outside. This can range from leaders, trainers and supplies (such as the Jedburgh assistance to the French Resistance), or a safe haven for overt activities (such as the NLF spokesmen in Hanoi).

External support need not be overt. Certain Shi'a groups in Iraq, for example, do receive assistance from Iran{{Citation needed|date=March 2009}}, but this is not a public position of the government of Iran, and may even be limited to factions of that government.  Early US support to the Afghan Northern Alliance against the Taliban used clandestine operators from both the [[CIA]] and [[United States Army Special Forces]]. As the latter conflict escalated, the US participation became overt.

Note that both [[unconventional warfare]] (UW) (guerrilla operations) and [[foreign internal defense]] (FID) (counterinsurgency) may be covert and use cellular organization.

In a covert FID mission, only selected host nation (HN) leaders are aware of the foreign support organization. Under [[Operation White Star]], US personnel gave covert FID assistance to the Royal Lao Army starting in 1959, became overt in 1961, and ceased operations in 1962.

==Models of insurgency and associated cell characteristics==
While different kinds of insurgency differ in where they place clandestine or covert cells, when certain types of insurgency grow in power, the cell system is deemphasized. Cells still may be used for leadership security, but, if overt violence by organized units becomes significant, cells are less important. In Mao's three-stage doctrine,&lt;ref name=Mao1967&gt;{{cite book
 | title = On Protracted War
 | author = Mao,  Zedong | authorlink = Mao Zedong
 | year = 1967
 | publisher = Foreign Language Press, Beijing
}}&lt;/ref&gt; cells are still useful in Phase II to give cover to part-time guerillas, but, as the insurgency creates full-time military units in Phase III, the main units are the focus, not the cells. The [[Eighth Route Army]] did not run on a cell model.

When considering where cells exist with respect to the existing government, the type of insurgency needs to be considered. One US Army reference was Field Manual 100-20, which has been superseded by FM3-07.&lt;ref name=FM3-07&gt;{{cite web
 | title = FM 3-07 (formerly FM 100-20): Stability Operations and Support Operations
 | date = 20 February 2003
 | author = US Department of the Army
 | url = https://atiam.train.army.mil/soldierPortal/atia/adlsc/view/altfmt/9630-1
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; Drawing on this work, Nyberg (a [[United States Marine Corps]] officer) extended the ideas to describe four types of cell system, although his descriptions also encompass types of insurgencies that the cell system supports.&lt;ref name=Nyberg&gt;{{Cite journal
 | title = Insurgency: The Unsolved Mystery
 | first = Eric N. | last = Nyberg
 | publisher = US Marine Corps University Command and Staff College
 | year = 1991
 | url = http://www.globalsecurity.org/military/library/report/1991/NEN.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt;  At present, there is a new type associated with transnational terrorist insurgencies.

# Traditional: the slowest to form, this reflects a principally indigenous insurgency, initially with limited goals. It is more secure than others, as it tends to grow from people with social, cultural or family ties. The insurgents resent a government that has failed to recognize  tribal, racial, religious or linguistic groups "who perceive that the government has denied their rights and interests and work to establish or restore them. They seldom seek to overthrow the government or control the whole society; however, they frequently attempt to withdraw from government control through autonomy or semiautonomy." The Mujahideen in Afghanistan and the Kurdish revolt in Iraq illustrate the traditional pattern of insurgency. [[al-Qaeda]] generally operates in this mode, but if they become strong enough in a given area, they may change to the mass-oriented form.
# Subversive: Usually driven by an organization that contains at least some of the governing elite, some being sympathizers already in place, and others who penetrate the government. When they use violence, it has a specific purpose, such as coercing voters, intimidating officials, and disrupting and discrediting the government. Typically, there is a political arm (such as  [[Sinn Féin]] or the [[Viet Cong|National Liberation Front]]) that directs the military in planning carefully coordinated violence. "Employment of violence is designed to show the system to be incompetent and to provoke the government to an excessively violent response which further undermines its legitimacy." The [[Nazi]] rise to power, in the 1930s, is another example of subversion. Nazi members of parliament and street fighters were hardly clandestine, but the overall plan of the Nazi leadership to gain control of the nation was hidden. "A subversive insurgency is suited to a more permissive political environment which allows the insurgents to use both legal and illegal methods to accomplish their goals. Effective government resistance may convert this to a critical-cell model.
# Critical-cell: Critical cell is useful when the political climate becomes less permissive than one that allowed shadow cells. While other cell types try to form intelligence cells within the government, this type sets up "[[Continuity of government|shadow government]]" cells that can seize power once the system is destroyed both by external means and the internal subversion. This model fits the classic [[coup d'etat]],&lt;ref name=Luttwak&gt;{{cite book
 | title = Coup d'etat: A Practical Handbook
 | year = 1968
 | author = Luttwak, Edward | authorlink = Edward Luttwak
 | publisher = Harvard University Press
}}&lt;/ref&gt; and often tries to minimize violence. Variants include the [[Sandinista]] takeover of an existing government weakened by external popular revolution. "Insurgents also seek to infiltrate the government's institutions, but their object is to destroy the system from within." Clandestine cells form inside the government. "The use of violence remains covert until the government is so weakened that the insurgency's superior organization seizes power, supported by the armed force. One variation of this pattern is when the insurgent leadership permits the popular revolution to destroy the existing government, then emerges to direct the formation of a new government. Another variation is seen in the [[Cuba]]n revolution&lt;ref name=Guevara&gt;{{cite book
 | author = Guevara, Ernesto "Che"
 | title = On Guerilla Warfare
 | publisher = Praeger
 | year = 1961
}}&lt;/ref&gt; and is referred to as the foco (or Cuban model) insurgency. This model involves a single, armed cell which emerges in the midst of degenerating government legitimacy and becomes the nucleus around which mass popular support rallies.  The insurgents use this support to establish control and erect new institutions."
# Mass-oriented: where the subversive and covert-cell systems work from within the government, the mass-oriented builds a government completely outside the existing one, with the intention of replacing it. Such "insurgents patiently construct a base of passive and active political supporters, while simultaneously building a large armed element of guerrilla and regular forces.  They plan a protracted campaign of increasing violence to destroy the government and its institutions from the outside.  They have a well-developed ideology and carefully determine their objectives.  They are highly organized and effectively use propaganda and guerrilla action to mobilize forces for a direct political and military challenge to the government." The revolution that produced the [[Peoples' Republic of China]], the [[American Revolution]], and the [[Shining Path]] insurgency in Peru are examples of the mass-oriented model. Once established, this type of insurgency is extremely difficult to defeat because of its great depth of organization.

==Classic models for cell system operations==
Different kinds of cell organizations have been used for different purposes. This section focuses on clandestine cells, as would be used for [[espionage]], [[sabotage]], or the organization for [[unconventional warfare]]. When unconventional warfare starts using overt units, the cell system tends to be used only for sensitive leadership and intelligence roles.&lt;ref name=Mao1967 /&gt; The examples here will use [[CIA cryptonym]]s as a naming convention used to identify members of the cell system. Cryptonyms begin with a two-letter country or subject name (e.g., AL), followed with an arbitrary word. It is considered elegant to have the code merge with the other letters to form a pronounceable word.

===Operations under official cover===
Station BERRY operates, for country B, in target country BE. It has three case officers and several support officers. Espionage operation run by case officers under diplomatic cover, they would have to with the basic recruiting methods described in this article. Case officer BETTY runs the local agents BEN and BEATLE. Case officer BESSIE runs BENSON and BEAGLE.
[[Image:Wdip-Cell-0.png|thumb|Representative diplomatic-cover station and networks]]

Some recruits, due to the sensitivity of their position or their personalities not being appropriate for cell leadership, might not enter cells but be run as singletons, perhaps by other than the recruiting case officer. Asset BARD is a different sort of highly sensitive singleton, who is a joint asset of the country B, and the country identified by prefix AR. ARNOLD is a case officer from the country AR embassy, who knows only the case officer BERTRAM and the security officer BEST. ARNOLD does not know the station chief of BERRY or any of its other personnel. Other than BELL and BEST, the Station personnel only know BERTRAM as someone authorized to be in the Station, and who is known for his piano playing at embassy parties. He is covered as Cultural Attache, in a country that has very few pianos. Only the personnel involved with BARD know that ARNOLD is other than another friendly diplomat.

In contrast, BESSIE and BETTY know one another, and procedures exist for their taking over each other's assets in the event one of the two is disabled.

Some recruits, however, would be qualified to recruit their own subcell, as BEATLE has done. BESSIE knows the identity of BEATLE-1 and BEATLE-2, since he had them checked by headquarters counterintelligence before they were recruited. Note that a cryptonym does not imply anything about its  designee, such as gender.

===Clandestine presence===
The diagram of "initial team presence" shows that two teams, ALAN and ALICE, have successfully entered an area of operation, the country coded AL, but are only aware of a pool of potential recruits, and have not yet actually recruited anyone. They communicate with one another only through headquarters, so compromise of one team will not affect the other.
[[Image:Wnoc-Cell-0.png|thumb|left |Initial team presence by 2 separate clandestine teams with no official cover]]

Assume that in team ALAN, ALASTAIR is one of the officers with local contacts, might recruit two cell leaders, ALPINE and ALTITUDE. The other local officer in the team, ALBERT, recruits ALLOVER.  When ALPINE recruited two subcell members, they would be referred to as ALPINE-1 and ALPINE-2.

ALPINE and ALTITUDE only know how to reach ALASTAIR, but they are aware of at least some of other team members' identity should ALASTAIR be unavailable, and they would accept a message from ALBERT. Most often, the identity (and location) of the radio operator may not be shared. ALPINE and ALTITUDE, however, do not know one another. They do not know any of the members of team ALICE.

The legitimacy of the subcell structure came from the recruitment process, originally by the case officer and then by the cell leaders. Sometimes, the cell leader would propose subcell member names to the case officer, so the case officer could have a headquarters name check run before bringing the individual into the subcell. In principle, however, the subcell members would know ALPINE, and sometimes the other members of the ALPINE cell if they needed to work together; if ALPINE-1 and ALPINE-2 had independent assignments, they might not know each other. ALPINE-1 and ALPINE-2 certainly would not know ALASTAIR or anyone in the ALTITUDE or ALLOVER cells.
[[Image:Wnoc-Cell-1.png|thumb|Clandestine teams have built initial subcells]]

As the networks grow, a subcell leader might create his own cell, so ALPINE-2 might become the leader of the ALIMONY cell.

===Fault-tolerant cellular structures===
Modern communications theory has introduced methods to increase fault tolerance in cell organizations. In the past, if cell members only knew the cell leader, and the leader was neutralized, the cell was cut off from the rest of the organization. Game theory and graph theory have been applied to the study of optimal covert network design (see Lindelauf, R.H.A. et al. 2009. The influence of secrecy on the communication structure of covert networks. Social Networks 31: 126-137).

If a traditional cell had independent communications with the foreign support organization, headquarters might be able to arrange its reconnection. Another method is to have impersonal communications "side links" between cells, such as a pair of [[dead drop]]s, one for Team ALAN to leave "lost contact" messages to be retrieved by Team ALICE, and another dead drop for Team ALICE to leave messages for Team ALAN.

These links, to be used only on losing contact, do not guarantee a contact. When a team finds a message in its emergency drop, it might do no more than send an alert message to headquarters. Headquarters might determine, through [[SIGINT]] or other sources, that the enemy had captured the leadership and the entire team, and order the other team not to attempt contact. If headquarters can have reasonable confidence that there is a communications failure or partial compromise, it might send a new contact to the survivors.

When the cut-off team has electronic communications, such as the Internet, it has a much better chance of eluding surveillance and getting emergency instructions than by using a dead drop that can be under physical surveillance.

==Non-traditional models, exemplified by al-Qaeda==
Due to cultural differences, assuming the ''al-Qaeda Training Manual''&lt;ref name=AQTM&gt;{{cite web
 | url = https://fas.org/irp/world/para/aqmanual.pdf
 |format=PDF| title = al-Qaeda training manual
 | publisher = US Southern District Court, US New York City Attorney's Office, entered as evidence in Africa embassy bombings
}}&lt;/ref&gt; is authentic, eastern cell structures may differ from the Western mode. "Al-Qaida's minimal core group, only accounting for the leadership, can also be viewed topologically as a ring or chain network, with each leader/node heading their own particular hierarchy.

"Such networks function by having their sub-networks provide information and other forms of support (the ‘many-to-one’ model), while the core group supplies ‘truth’ and decisions/directions (the ‘one-to-many’ model). Trust and personal relationships are an essential part of the Al-Qaida network (a limiting factor, even while it provides enhanced security). Even while cell members are trained as ‘replaceable’ units, ‘vetting’ of members occurs during the invited training period under the observation of the core group.&lt;ref name=Sleepers&gt;{{cite web
 | url = http://www.metatempo.com/huntingthesleepers.pdf
 |format=PDF| title = Hunting the Sleepers: Tracking al-Qaida's Covert Operatives
 | date = 2001-12-31
 | author = Decision Support Systems, Inc.
 | accessdate = 2007-11-17
}}&lt;/ref&gt;

Cells of this structure are built outwards, from an internal leadership core. Superficially, this might be likened to a Western cell structure that emanates from a headquarters, but the Western centrality is bureaucratic, while structures in other non-western cultures builds on close personal relationships, often built over years, perhaps involving family or other in-group linkages. Such in-groups are thus extremely hard to infiltrate; infiltration has a serious chance only outside the in-group. Still, it may be possible for an in-group to be compromised through [[COMINT]] or, in rare cases, by compromising a member.

The core group is logically a ring, but is superimposed on an inner hub-and-spoke structure of ideological authority. Each member of the core forms another hub and spoke system (see [[#Infrastructure cells|infrastructure cells]]), the spokes leading to infrastructure cells under the supervision of the core group member, and possibly to operational groups which the headquarters support. Note that in this organization, there is a point at which the operational cell becomes autonomous of the core. Members surviving the operation may rejoin at various points.
[[Image:T-Cell-0.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

Osama, in this model, has the main responsibility of commanding the organization and being the spokesman on propaganda video and audio messages distributed by the propaganda cell. The other members of the core each command one or more infrastructure cells.

While the tight coupling enhances security, it can limit flexibility and the ability to scale the organization. This in-group, while sharing tight cultural and ideological values, is not committed to a bureaucratic process.

"Members of the core group are under what could be termed 'positive control'—long relationships
and similar mindsets make 'control' not so much of an issue, but there are distinct roles, and position (structural, financial, spiritual) determines authority, thus making the core group a hierarchy topologically.&lt;ref name=Sleepers /&gt;

In the first example of the core, each member knows how to reach two other members, and also knows the member(s) he considers his ideological superior. Solid lines show basic communication, dotted red arrows show the first level of ideological respect, and dotted blue arrows show a second level of ideological respect.

If Osama, the most respected, died, the core would reconstitute itself. While different members have an individual ideological guide, and these are not the same for all members, the core would reconstitute itself with Richard as most respected.

Assume there are no losses, and Osama can be reached directly only by members of the core group. Members of outer cells and support systems might know him only as "the Commander", or, as in the actual case of al-Qaeda, Osama bin Laden's face is recognizable worldwide, but only a few people know where he was or even how to contact him.

===Infrastructure cells===
Any clandestine or covert service, especially a non-national one, needs a variety of technical and administrative functions. Some of these services include:&lt;ref name=Sleepers /&gt;

# Forged documents and counterfeit currency
# Apartments and hiding places
# Communication means
# Transportation means
# Information
# Arms and ammunition
# Transport

Other functions include psychological operations, training, and finance.

A national intelligence service&lt;ref name=CIAsupport&gt;{{cite web
 | url = https://www.cia.gov/offices-of-cia/mission-support/who-we-are.html
 | author = US Central Intelligence Agency
 | title = Support to Mission: Who We Are
 | accessdate = 2007-11-19
}}&lt;/ref&gt;
has a support organization to deal with services such as finance, logistics, facilities (e.g., [[#Safehouses and Other Meeting Places|safehouses]]), information technology, communications, training, weapons and explosives, medical services, etc. Transportation alone is a huge function, including the need to buy tickets without drawing suspicion, and, where appropriate, using private vehicles. Finance includes the need to transfer money without coming under the suspicion of financial security organizations.

Some of these functions, such as finance, are far harder to operate in remote areas, such as the [[FATA]] of [[Pakistan]], than in cities with large numbers of official and unofficial financial institutions, and the communications to support them. If the financial office is distant from the remote headquarters, there is a need for [[couriers]], who must be trusted to some extent, but they may not know the contents of their messages or the actual identity of sender and/or receiver. The couriers, depending on the balance among type and size of message, security, and technology available, may memorize messages, carry audio or video recordings, or hand-carry computer media.
[[Image:T-Cell-1.png|thumb|Core group and infrastructure cells; military cells in training]]

"These cells are socially embedded (less so than the core group, however), structurally embedded, functionally embedded (they are specialized into a domain), and knowledge base-specific (there does not seem to be a great deal of cross-training, or lateral mobility in the organization). Such cells are probably subjected to a mixture of positive and negative control ("do this, do these sorts of things, don’t do that")."&lt;ref name=Sleepers /&gt;

{| class="wikitable"
&lt;caption&gt;Core Structure of Non-National Group&lt;/caption&gt;
|-
! Member
! Infrastructure commanded
|-
| Richard
| Finance
|-
| Anton
| Military training/operations 1
|-
| Hassan
| Military training/operations 2
|-
| David
| Transportation
|-
| Kim
| Communications and propaganda
|}

The leaders of military cells are responsible for training them, and, when an operation is scheduled, selecting the operational commander, giving him the basic objective and arranging whatever support is needed, and then release him from tight control to execute the meeting. Depending on the specific case, the military leaders might have direct, possibly one-way, communications with their cells, or they might have to give Kim the messages to be transmitted, by means that Anton and Hassan have no need to know.

Note that Anton does not have a direct connection to Kim. Under normal circumstances, he sacrifices efficiency for security, by passing communications requests through Hassan. The security structure also means that Hassan does not know the members of Anton's cells, and Kim may know only ways to communicate with them but not their identity.

Kim operates two systems of cells, one for secure communications and one for propaganda. To send out a propaganda message, Osama must pass it to Kim. If Kim were compromised, the core group might have significant problems with any sort of outside communications.

Terrorist networks do not match cleanly to other cell systems that regularly report to a headquarters. The apparent al-Qaeda methodology of letting operational cells decide on their final dates and means of attack exhibit an operational pattern, but not a periodicity that could easily be used for an [[Intelligence analysis management#Indications &amp; warning checklists|indications checklist]] appropriate for a warning center. Such lists depend on seeing a local pattern to give a specific warning.&lt;ref name=Vos&gt;{{cite web
 | title = Modeling Terrorist Networks - Complex Systems at the Mid-Range
 | first1 = Philip Vos
 | last1 = Fellman
 | first2 = Roxana
 | last2 = Wright
 | url = http://www.psych.lse.ac.uk/complexity/Conference/FellmanWright.pdf
 |format=PDF| accessdate = 2007-11-02
}}&lt;/ref&gt;

Note that Hassan has two subordinates that have not yet established operational cells. These subordinates can be considered '''sleepers''', but not necessarily with a sleeper cell.

===Operational cells===
For each mission are created one or more operational cells. If the al-Qaeda signature of multiple concurrent attacks is used, there may be an operational cell for each target location. It will depend on the operation if they will need any support cells in the operational area. For example, it may be more secure to have a local cell build bombs, which will be delivered by cells coming from outside the area.

"Operational cells are not created, but instead 'seeded' utilizing individuals spotted or that request assistance (both groups are 'vetted' by being trained under the observation of the core group, which dramatically restricts the opportunity for passing off walk-ins under false flag). Categorization of operational cells appears to be by capabilities, region, and then task/operation. Operational cells are composed of members whose worldview has been firmly tested—necessary to front-load, because such cells are dispersed back to their own local control (or negative control—proscribed behavior—with positive control only coming in the form of contact for synchronization or support)."&lt;ref name=Sleepers /&gt;

If operational cells routinely are "released" ''curved dotted lines on link to military cells'' to select their final operational parameters, they use a different paradigm than governmental clandestine or covert operations. On a number of cases, US special operations forces had to wait for Presidential authorization to make an attack, or even move to staging areas. Admittedly, a country would have to face the consequences of an inappropriate attack, so it may tend to be overcautious, where a terror network would merely shrug at the world being upset. Assuming that the al-Qaeda operational technique is not to use positive control, their operations may be more random, but also more unpredictable for counterterror forces. If their cells truly need constant control, there are communications links that might be detected by SIGINT, and if their command can be disrupted, the field units could not function. Since there is fairly little downside for terrorists to attack out of synchronization with other activities, the lack of positive control becomes a strength of their approach to cell organization.
[[Image:T-Cell-2.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

The operational cells need to have continuous internal communication; there is a commander, who may be in touch with infrastructure cells or, less likely from a security standpoint with the core group.

Al-Qaeda's approach, which even differs from that of earlier terrorist organizations, may be very viable for their goals:

* Cells are redundant and distributed, making them difficult to ‘roll up’
* Cells are coordinated, not under "command &amp; control"—this autonomy and local control makes them flexible, and enhances security
* Trust and comcon internally to the cell provide redundancy of potential command (a failure of Palestinian operations in the past), and well as a shared knowledgebase (which may mean, over time, that ‘cross training’ emerges inside a cell, providing redundancy of most critical skills and knowledge).&lt;ref name=Sleepers /&gt;

===Indirect support networks===
In the above graphic, note the indirect support network controlled by Richard's subcell.

"While Al-Qaida has elements of the organization designed to support the structure, but such elements are insufficient in meeting the needs of such an organization, and for security reasons there would be redundant and secondary-/tertiary-networks that are unaware of their connection to Al-Qaida. These networks, primarily related to fundraising and financial activities, as well as technology providers, are in a ‘use’ relationship with Al-Qaida—managed through cut-outs or individuals that do not inform them of the nature of activities, and that may have a cover pretext sufficient to deflect questions or inquiry."&lt;ref name=Sleepers /&gt;

===A possible countermeasure===
In 2002, ''U.S. News &amp; World Report'' said that American intelligence is beginning to acquire a sufficiently critical mass of intelligence on al-Qaida indicating, "Once thought nearly impossible to penetrate, al Qaeda is proving no tougher a target than the KGB or the Mafia--closed societies that took the U.S. government years to get inside. "We're getting names, the different camps they trained at, the hierarchy, the infighting," says an intelligence official. "It's very promising."&lt;ref name=Kaplan2002&gt;{{Cite journal
 | title = Run and Gun: Al Qaeda arrests and intelligence hauls bring new energy to the war on terrorism
 | first = David E. | last = Kaplan
 | date = 22 September 2002
 | journal = U.S. News &amp; World Report
 | url = http://www.usnews.com/usnews/news/articles/020930/archive_022824.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; The report also said that the collected data has allowed the recruiting of informants.

Writing in the U.S. Army journal ''Military Review'', David W. Pendall  suggested that a "catch-and-release program for suspected operatives might create reluctance or distrust in such suspects and prevent them from further acts or, perhaps more important, create distrust in the cell leaders of these individuals in the future." The author noted the press release describing Ramzi Binalshib's cooperation with the United States "are sure to prevent reentry into a terrorist cell as a trusted member and most likely limits the further trust and assignments of close cell associates still at large. The captor would determine when to name names and when to remain silent."&lt;ref name=Pendall2004&gt;{{Cite journal
 | date = January–February 2004
 | journal = Military Review
 | url = http://calldp.leavenworth.army.mil
 | first = David W. | last = Pendall
 | title =Effects-Based Operations and the Exercise of National Power
 | publisher = [[United States Army Combined Arms Center]]
 | postscript = &lt;!--None--&gt;
}}  Find the article by going through the Military Review directories&lt;/ref&gt; Indeed, once intelligence learns the name and characteristics of an at-large adversary, as well as some sensitive information that would plausibly be known to him, a news release could be issued to talk about his cooperation. Such a method could not be used too often, but, used carefully, could disturb the critical trust networks. The greatest uncertainty might be associated with throwing doubt onto a key member of an operational cell that has gone autonomous.

==See also==
* [[Leaderless resistance]]
* [[Lone wolf (terrorism)]]

==References==
{{reflist | 2}}

==External links==
* [http://theriskyshift.com/2012/06/an-introduction-to-terrorist-organisational-structures/ An Introduction To Terrorist Organisational Structures]

{{Intelligence cycle management}}

[[Category:Counter-intelligence]]
[[Category:Types of espionage]]
[[Category:Intelligence analysis]]
[[Category:Military intelligence]]
[[Category:Military tactics]]
[[Category:Secrecy]]
[[Category:Terrorism tactics]]

[http://www.cimacell.com/wiki/index.php?title=Structure Reachback Ops]</text>
    <sha1>0891f4ea30f20cf531adbd72ac5f1baaf89bb9e8</sha1>
  </revision>
  <revision>
    <id>89</id>
    <parentid>88</parentid>
    <timestamp>2015-12-27T01:37:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39486" xml:space="preserve">__NOEDITSECTION__

{{for|the general use of a cellular structure by an organization, such as by a business|Cellular organization (disambiguation)}}
{{redirect|Sleeper cell}}
{{Use dmy dates|date=July 2011}}
{{multiple issues|
{{Essay-like|date=July 2011}}
{{POV|date=September 2012}}
{{Original research|date=January 2015}}
{{cleanup|reason=Poorly written, poorly referenced, marked essay-like (mostly user Hcberkowitz's edits; see page history) and POV issues and generally underlinked|date=January 2015}}
{{cleanup-rewrite|date=January 2015}}
{{Expert-subject|date=January 2015}}
}}

{{terrorism}}
A '''clandestine cell''' structure is a method for organizing a group of people like [[French resistance|resistance]] fighters or terrorists in such a way that it can more effectively resist penetration by an opposing organization (e.g., a law enforcement organization). In a cell structure, each small group of people in the cell only know the identities of the people in their cell; as such, if a cell member is apprehended and interrogated, he or she will not know the identities of the higher-ranking individuals in the organization. Depending on the group's [[philosophy]], its operational area, the communications technologies available, and the nature of the mission, it can range from a strict hierarchy to an extremely distributed organization. It is also a method used by [[organized crime|criminal organizations]], [[undercover]] operatives, and unconventional warfare (UW) units led by [[special forces]]. Historically, clandestine organizations have avoided electronic communications, because [[signals intelligence]] is a strength of conventional militaries and counterintelligence organizations.{{citation needed|date=August 2012}}

In the context of [[tradecraft]], [[covert operation|covert]] and [[clandestine operation|clandestine]] are not synonymous. As noted in the definition (which has been used by the United States and NATO since World War II) in a covert operation the identity of the sponsor is concealed, while in a clandestine operation the operation itself is concealed. Put differently, clandestine means "hidden", while covert means "deniable". The adversary is aware that a covert activity is happening, but does not know who is doing it, and certainly not their sponsorship. Clandestine activities, however, if successful, are completely unknown to the adversary, and their function, such as espionage, would be neutralized if there was any awareness of the activity.

A '''sleeper cell''' refers to a cell, or isolated grouping of [[sleeper agent]]s that lies dormant until it receives orders or decides to act.

==History==

=== Provisional Irish Republican Army===
As opposed to the [[French Resistance]], the modern [[Provisional Irish Republican Army]] (PIRA) has a history going back to Irish revolutionary forces in the early 20th century, but has little external control.  Its doctrine and organization have changed over time, given factors such as the independence of 26 of Ireland's 32 counties, the continued British control of Northern Ireland and the simple passage of time and changes in contemporary thinking and technology.&lt;ref name=Leahy&gt;{{cite web
 | url = http://cgsc.cdmhost.com/cgi-bin/showfile.exe?CISOROOT=/p4013coll2&amp;CISOPTR=386&amp;filename=387.pdf
 |format=PDF| author = Leahy, Kevin C.
 | year = 2005
 | title = The Impact of Technology on the Command, Control, and Organizational Structure of Insurgent Groups
 | accessdate=2007-12-04
}}&lt;/ref&gt;

Officially, the PIRA is hierarchical, but, especially as British security forces became more effective, changed to a semiautonomous model for its operational and certain of its support cells (e.g., transportation, intelligence, cover and security).&lt;ref name=GreenBook&gt;{{cite web
 | url = https://web.archive.org/web/20110606012137/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html
 | author = Irish Republican Army
 | title = The Green Book
 | accessdate=2007-12-04
|archiveurl=https://web.archive.org/web/20070616132240/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html|archivedate=2007-06-16}}&lt;/ref&gt; Its leadership sees itself as guiding and consensus-building. The lowest-level cells, typically of 2-5 people, tend to be built by people with an existing personal relationship. British counterinsurgents could fairly easily understand the command structure, but not the workings of the operational cells.

The IRA has an extensive network of inactive or sleeper cells, so new ''ad hoc'' organizations may appear for any specific operation.

===World War II French Resistance===
In World War II, [[Operation Jedburgh]] teams parachuted into occupied France to lead unconventional warfare units.&lt;ref name=Hall&gt;{{cite book
 | author = Hall, Roger
 | title = You're Stepping on my Cloak and Dagger
 | publisher = Bantam Books
 | year =1964
}}&lt;/ref&gt;&lt;ref name=SOETO&gt;{{cite book
 | chapterurl = http://www.history.army.mil/books/wwii/70-42/70-423.htm
 | chapter = Chapter 3: Special Operations in the European Theater
 | publisher = [[United States Army Center of Military History]]
| url = http://www.history.army.mil/books/wwii/70-42/70-42c.htm
| title = U.S. Army Special Operations in World War II
| first = David W.
| last = Hogan
| id = CMH Pub 70-42
|year = 1992
| location = Washington, D.C.
}}&lt;/ref&gt; They would be composed of two officers, one American or British, and the other French, the latter preferably from the area into which they landed. The third member of the team was a radio operator.

Especially through the French member, they would contact trusted individuals in the area of operation, and ask them to recruit a team of trusted subordinates (i.e., a subcell). If the team mission were sabotage, reconnaissance, or espionage, there was no need to meet in large units. If the team was to carry out direct action, often an unwise mission unless an appreciable number of the locals had military experience, it would be necessary to assemble into units for combat. Even then, the hideouts of the leadership were known only to subcell leaders. The legitimacy of the Jedburgh team came from its known affiliation with Allied powers, and it was a structure more appropriate for UW than for truly clandestine operations.

===National Front for the Liberation of South Vietnam===
Also known as the [[Viet Cong]], this organization grew from earlier anticolonial groups fighting the French, as well as anti-Japanese guerillas during World War II.&lt;ref name=VietCong&gt;{{cite book
 | author = Pike, Douglas
 | title = Viet Cong: Organization and Technique of the National Liberation Front of South Vietnam
 | publisher = MIT Press
 | year = 1970
}}&lt;/ref&gt;
Its command, control, and communication techniques derived from the experiences of these earlier insurgent groups. The group had extensive support from North Vietnam, and, indirectly, from the Soviet Union. It had parallel political and military structures, often overlapping. See [[Viet Cong and PAVN strategy and tactics]].
[[Image:Vcnvastructure4rev.jpg|thumb|right |A dual, but sometimes overlapping, Party and Military structure was top-down]]
The lowest level consisted of three-person cells who operated quite closely, and engaging in the sort of [[self-criticism]] common, as a bonding method, to Communist organizations.{{Citation needed|date=June 2014}}

==Parallel organizations==
The NLF and PIRA, as well as other movements, have chosen to have parallel political and military organizations. In the case of the NLF, other than some individuals with sanctuary in North Vietnam, the political organization could not be overt during the [[Vietnam War]]. After the war ended, surviving NLF officials held high office.

In the case of the PIRA, its political wing, [[Sinn Féin]], became increasingly overt, and then a full participant in politics. [[Hamas]] and [[Hezbollah]] also have variants of overt political/social service and covert military wings.

The overt political/social–covert military split avoided the inflexibility of a completely secret organization. Once an active insurgency began, the secrecy {{clarify span|could limit|date=January 2015}}&lt;!-- what? --&gt; freedom of action, distort information about goals and ideals, and restrict communication within the insurgency.&lt;ref name=FM3-24&gt;{{cite web
 | title = FM 3-24: Counterinsurgency
 | author = US Department of the Army
 |date=December 2006
 | url = https://fas.org/irp/doddir/army/fm3-24.pdf
|format=PDF}}&lt;/ref&gt; In a split organization, the public issues can be addressed overtly, while military actions were kept covert and intelligence functions stay clandestine.

==External support==
Many cell systems still receive, with due attention to security, support from the outside. This can range from leaders, trainers and supplies (such as the Jedburgh assistance to the French Resistance), or a safe haven for overt activities (such as the NLF spokesmen in Hanoi).

External support need not be overt. Certain Shi'a groups in Iraq, for example, do receive assistance from Iran{{Citation needed|date=March 2009}}, but this is not a public position of the government of Iran, and may even be limited to factions of that government.  Early US support to the Afghan Northern Alliance against the Taliban used clandestine operators from both the [[CIA]] and [[United States Army Special Forces]]. As the latter conflict escalated, the US participation became overt.

Note that both [[unconventional warfare]] (UW) (guerrilla operations) and [[foreign internal defense]] (FID) (counterinsurgency) may be covert and use cellular organization.

In a covert FID mission, only selected host nation (HN) leaders are aware of the foreign support organization. Under [[Operation White Star]], US personnel gave covert FID assistance to the Royal Lao Army starting in 1959, became overt in 1961, and ceased operations in 1962.

==Models of insurgency and associated cell characteristics==
While different kinds of insurgency differ in where they place clandestine or covert cells, when certain types of insurgency grow in power, the cell system is deemphasized. Cells still may be used for leadership security, but, if overt violence by organized units becomes significant, cells are less important. In Mao's three-stage doctrine,&lt;ref name=Mao1967&gt;{{cite book
 | title = On Protracted War
 | author = Mao,  Zedong | authorlink = Mao Zedong
 | year = 1967
 | publisher = Foreign Language Press, Beijing
}}&lt;/ref&gt; cells are still useful in Phase II to give cover to part-time guerillas, but, as the insurgency creates full-time military units in Phase III, the main units are the focus, not the cells. The [[Eighth Route Army]] did not run on a cell model.

When considering where cells exist with respect to the existing government, the type of insurgency needs to be considered. One US Army reference was Field Manual 100-20, which has been superseded by FM3-07.&lt;ref name=FM3-07&gt;{{cite web
 | title = FM 3-07 (formerly FM 100-20): Stability Operations and Support Operations
 | date = 20 February 2003
 | author = US Department of the Army
 | url = https://atiam.train.army.mil/soldierPortal/atia/adlsc/view/altfmt/9630-1
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; Drawing on this work, Nyberg (a [[United States Marine Corps]] officer) extended the ideas to describe four types of cell system, although his descriptions also encompass types of insurgencies that the cell system supports.&lt;ref name=Nyberg&gt;{{Cite journal
 | title = Insurgency: The Unsolved Mystery
 | first = Eric N. | last = Nyberg
 | publisher = US Marine Corps University Command and Staff College
 | year = 1991
 | url = http://www.globalsecurity.org/military/library/report/1991/NEN.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt;  At present, there is a new type associated with transnational terrorist insurgencies.

# Traditional: the slowest to form, this reflects a principally indigenous insurgency, initially with limited goals. It is more secure than others, as it tends to grow from people with social, cultural or family ties. The insurgents resent a government that has failed to recognize  tribal, racial, religious or linguistic groups "who perceive that the government has denied their rights and interests and work to establish or restore them. They seldom seek to overthrow the government or control the whole society; however, they frequently attempt to withdraw from government control through autonomy or semiautonomy." The Mujahideen in Afghanistan and the Kurdish revolt in Iraq illustrate the traditional pattern of insurgency. [[al-Qaeda]] generally operates in this mode, but if they become strong enough in a given area, they may change to the mass-oriented form.
# Subversive: Usually driven by an organization that contains at least some of the governing elite, some being sympathizers already in place, and others who penetrate the government. When they use violence, it has a specific purpose, such as coercing voters, intimidating officials, and disrupting and discrediting the government. Typically, there is a political arm (such as  [[Sinn Féin]] or the [[Viet Cong|National Liberation Front]]) that directs the military in planning carefully coordinated violence. "Employment of violence is designed to show the system to be incompetent and to provoke the government to an excessively violent response which further undermines its legitimacy." The [[Nazi]] rise to power, in the 1930s, is another example of subversion. Nazi members of parliament and street fighters were hardly clandestine, but the overall plan of the Nazi leadership to gain control of the nation was hidden. "A subversive insurgency is suited to a more permissive political environment which allows the insurgents to use both legal and illegal methods to accomplish their goals. Effective government resistance may convert this to a critical-cell model.
# Critical-cell: Critical cell is useful when the political climate becomes less permissive than one that allowed shadow cells. While other cell types try to form intelligence cells within the government, this type sets up "[[Continuity of government|shadow government]]" cells that can seize power once the system is destroyed both by external means and the internal subversion. This model fits the classic [[coup d'etat]],&lt;ref name=Luttwak&gt;{{cite book
 | title = Coup d'etat: A Practical Handbook
 | year = 1968
 | author = Luttwak, Edward | authorlink = Edward Luttwak
 | publisher = Harvard University Press
}}&lt;/ref&gt; and often tries to minimize violence. Variants include the [[Sandinista]] takeover of an existing government weakened by external popular revolution. "Insurgents also seek to infiltrate the government's institutions, but their object is to destroy the system from within." Clandestine cells form inside the government. "The use of violence remains covert until the government is so weakened that the insurgency's superior organization seizes power, supported by the armed force. One variation of this pattern is when the insurgent leadership permits the popular revolution to destroy the existing government, then emerges to direct the formation of a new government. Another variation is seen in the [[Cuba]]n revolution&lt;ref name=Guevara&gt;{{cite book
 | author = Guevara, Ernesto "Che"
 | title = On Guerilla Warfare
 | publisher = Praeger
 | year = 1961
}}&lt;/ref&gt; and is referred to as the foco (or Cuban model) insurgency. This model involves a single, armed cell which emerges in the midst of degenerating government legitimacy and becomes the nucleus around which mass popular support rallies.  The insurgents use this support to establish control and erect new institutions."
# Mass-oriented: where the subversive and covert-cell systems work from within the government, the mass-oriented builds a government completely outside the existing one, with the intention of replacing it. Such "insurgents patiently construct a base of passive and active political supporters, while simultaneously building a large armed element of guerrilla and regular forces.  They plan a protracted campaign of increasing violence to destroy the government and its institutions from the outside.  They have a well-developed ideology and carefully determine their objectives.  They are highly organized and effectively use propaganda and guerrilla action to mobilize forces for a direct political and military challenge to the government." The revolution that produced the [[Peoples' Republic of China]], the [[American Revolution]], and the [[Shining Path]] insurgency in Peru are examples of the mass-oriented model. Once established, this type of insurgency is extremely difficult to defeat because of its great depth of organization.

==Classic models for cell system operations==
Different kinds of cell organizations have been used for different purposes. This section focuses on clandestine cells, as would be used for [[espionage]], [[sabotage]], or the organization for [[unconventional warfare]]. When unconventional warfare starts using overt units, the cell system tends to be used only for sensitive leadership and intelligence roles.&lt;ref name=Mao1967 /&gt; The examples here will use [[CIA cryptonym]]s as a naming convention used to identify members of the cell system. Cryptonyms begin with a two-letter country or subject name (e.g., AL), followed with an arbitrary word. It is considered elegant to have the code merge with the other letters to form a pronounceable word.

===Operations under official cover===
Station BERRY operates, for country B, in target country BE. It has three case officers and several support officers. Espionage operation run by case officers under diplomatic cover, they would have to with the basic recruiting methods described in this article. Case officer BETTY runs the local agents BEN and BEATLE. Case officer BESSIE runs BENSON and BEAGLE.
[[Image:Wdip-Cell-0.png|thumb|Representative diplomatic-cover station and networks]]

Some recruits, due to the sensitivity of their position or their personalities not being appropriate for cell leadership, might not enter cells but be run as singletons, perhaps by other than the recruiting case officer. Asset BARD is a different sort of highly sensitive singleton, who is a joint asset of the country B, and the country identified by prefix AR. ARNOLD is a case officer from the country AR embassy, who knows only the case officer BERTRAM and the security officer BEST. ARNOLD does not know the station chief of BERRY or any of its other personnel. Other than BELL and BEST, the Station personnel only know BERTRAM as someone authorized to be in the Station, and who is known for his piano playing at embassy parties. He is covered as Cultural Attache, in a country that has very few pianos. Only the personnel involved with BARD know that ARNOLD is other than another friendly diplomat.

In contrast, BESSIE and BETTY know one another, and procedures exist for their taking over each other's assets in the event one of the two is disabled.

Some recruits, however, would be qualified to recruit their own subcell, as BEATLE has done. BESSIE knows the identity of BEATLE-1 and BEATLE-2, since he had them checked by headquarters counterintelligence before they were recruited. Note that a cryptonym does not imply anything about its  designee, such as gender.

===Clandestine presence===
The diagram of "initial team presence" shows that two teams, ALAN and ALICE, have successfully entered an area of operation, the country coded AL, but are only aware of a pool of potential recruits, and have not yet actually recruited anyone. They communicate with one another only through headquarters, so compromise of one team will not affect the other.
[[Image:Wnoc-Cell-0.png|thumb|left |Initial team presence by 2 separate clandestine teams with no official cover]]

Assume that in team ALAN, ALASTAIR is one of the officers with local contacts, might recruit two cell leaders, ALPINE and ALTITUDE. The other local officer in the team, ALBERT, recruits ALLOVER.  When ALPINE recruited two subcell members, they would be referred to as ALPINE-1 and ALPINE-2.

ALPINE and ALTITUDE only know how to reach ALASTAIR, but they are aware of at least some of other team members' identity should ALASTAIR be unavailable, and they would accept a message from ALBERT. Most often, the identity (and location) of the radio operator may not be shared. ALPINE and ALTITUDE, however, do not know one another. They do not know any of the members of team ALICE.

The legitimacy of the subcell structure came from the recruitment process, originally by the case officer and then by the cell leaders. Sometimes, the cell leader would propose subcell member names to the case officer, so the case officer could have a headquarters name check run before bringing the individual into the subcell. In principle, however, the subcell members would know ALPINE, and sometimes the other members of the ALPINE cell if they needed to work together; if ALPINE-1 and ALPINE-2 had independent assignments, they might not know each other. ALPINE-1 and ALPINE-2 certainly would not know ALASTAIR or anyone in the ALTITUDE or ALLOVER cells.
[[Image:Wnoc-Cell-1.png|thumb|Clandestine teams have built initial subcells]]

As the networks grow, a subcell leader might create his own cell, so ALPINE-2 might become the leader of the ALIMONY cell.

===Fault-tolerant cellular structures===
Modern communications theory has introduced methods to increase fault tolerance in cell organizations. In the past, if cell members only knew the cell leader, and the leader was neutralized, the cell was cut off from the rest of the organization. Game theory and graph theory have been applied to the study of optimal covert network design (see Lindelauf, R.H.A. et al. 2009. The influence of secrecy on the communication structure of covert networks. Social Networks 31: 126-137).

If a traditional cell had independent communications with the foreign support organization, headquarters might be able to arrange its reconnection. Another method is to have impersonal communications "side links" between cells, such as a pair of [[dead drop]]s, one for Team ALAN to leave "lost contact" messages to be retrieved by Team ALICE, and another dead drop for Team ALICE to leave messages for Team ALAN.

These links, to be used only on losing contact, do not guarantee a contact. When a team finds a message in its emergency drop, it might do no more than send an alert message to headquarters. Headquarters might determine, through [[SIGINT]] or other sources, that the enemy had captured the leadership and the entire team, and order the other team not to attempt contact. If headquarters can have reasonable confidence that there is a communications failure or partial compromise, it might send a new contact to the survivors.

When the cut-off team has electronic communications, such as the Internet, it has a much better chance of eluding surveillance and getting emergency instructions than by using a dead drop that can be under physical surveillance.

==Non-traditional models, exemplified by al-Qaeda==
Due to cultural differences, assuming the ''al-Qaeda Training Manual''&lt;ref name=AQTM&gt;{{cite web
 | url = https://fas.org/irp/world/para/aqmanual.pdf
 |format=PDF| title = al-Qaeda training manual
 | publisher = US Southern District Court, US New York City Attorney's Office, entered as evidence in Africa embassy bombings
}}&lt;/ref&gt; is authentic, eastern cell structures may differ from the Western mode. "Al-Qaida's minimal core group, only accounting for the leadership, can also be viewed topologically as a ring or chain network, with each leader/node heading their own particular hierarchy.

"Such networks function by having their sub-networks provide information and other forms of support (the ‘many-to-one’ model), while the core group supplies ‘truth’ and decisions/directions (the ‘one-to-many’ model). Trust and personal relationships are an essential part of the Al-Qaida network (a limiting factor, even while it provides enhanced security). Even while cell members are trained as ‘replaceable’ units, ‘vetting’ of members occurs during the invited training period under the observation of the core group.&lt;ref name=Sleepers&gt;{{cite web
 | url = http://www.metatempo.com/huntingthesleepers.pdf
 |format=PDF| title = Hunting the Sleepers: Tracking al-Qaida's Covert Operatives
 | date = 2001-12-31
 | author = Decision Support Systems, Inc.
 | accessdate = 2007-11-17
}}&lt;/ref&gt;

Cells of this structure are built outwards, from an internal leadership core. Superficially, this might be likened to a Western cell structure that emanates from a headquarters, but the Western centrality is bureaucratic, while structures in other non-western cultures builds on close personal relationships, often built over years, perhaps involving family or other in-group linkages. Such in-groups are thus extremely hard to infiltrate; infiltration has a serious chance only outside the in-group. Still, it may be possible for an in-group to be compromised through [[COMINT]] or, in rare cases, by compromising a member.

The core group is logically a ring, but is superimposed on an inner hub-and-spoke structure of ideological authority. Each member of the core forms another hub and spoke system (see [[#Infrastructure cells|infrastructure cells]]), the spokes leading to infrastructure cells under the supervision of the core group member, and possibly to operational groups which the headquarters support. Note that in this organization, there is a point at which the operational cell becomes autonomous of the core. Members surviving the operation may rejoin at various points.
[[Image:T-Cell-0.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

Osama, in this model, has the main responsibility of commanding the organization and being the spokesman on propaganda video and audio messages distributed by the propaganda cell. The other members of the core each command one or more infrastructure cells.

While the tight coupling enhances security, it can limit flexibility and the ability to scale the organization. This in-group, while sharing tight cultural and ideological values, is not committed to a bureaucratic process.

"Members of the core group are under what could be termed 'positive control'—long relationships
and similar mindsets make 'control' not so much of an issue, but there are distinct roles, and position (structural, financial, spiritual) determines authority, thus making the core group a hierarchy topologically.&lt;ref name=Sleepers /&gt;

In the first example of the core, each member knows how to reach two other members, and also knows the member(s) he considers his ideological superior. Solid lines show basic communication, dotted red arrows show the first level of ideological respect, and dotted blue arrows show a second level of ideological respect.

If Osama, the most respected, died, the core would reconstitute itself. While different members have an individual ideological guide, and these are not the same for all members, the core would reconstitute itself with Richard as most respected.

Assume there are no losses, and Osama can be reached directly only by members of the core group. Members of outer cells and support systems might know him only as "the Commander", or, as in the actual case of al-Qaeda, Osama bin Laden's face is recognizable worldwide, but only a few people know where he was or even how to contact him.

===Infrastructure cells===
Any clandestine or covert service, especially a non-national one, needs a variety of technical and administrative functions. Some of these services include:&lt;ref name=Sleepers /&gt;

# Forged documents and counterfeit currency
# Apartments and hiding places
# Communication means
# Transportation means
# Information
# Arms and ammunition
# Transport

Other functions include psychological operations, training, and finance.

A national intelligence service&lt;ref name=CIAsupport&gt;{{cite web
 | url = https://www.cia.gov/offices-of-cia/mission-support/who-we-are.html
 | author = US Central Intelligence Agency
 | title = Support to Mission: Who We Are
 | accessdate = 2007-11-19
}}&lt;/ref&gt;
has a support organization to deal with services such as finance, logistics, facilities (e.g., [[#Safehouses and Other Meeting Places|safehouses]]), information technology, communications, training, weapons and explosives, medical services, etc. Transportation alone is a huge function, including the need to buy tickets without drawing suspicion, and, where appropriate, using private vehicles. Finance includes the need to transfer money without coming under the suspicion of financial security organizations.

Some of these functions, such as finance, are far harder to operate in remote areas, such as the [[FATA]] of [[Pakistan]], than in cities with large numbers of official and unofficial financial institutions, and the communications to support them. If the financial office is distant from the remote headquarters, there is a need for [[couriers]], who must be trusted to some extent, but they may not know the contents of their messages or the actual identity of sender and/or receiver. The couriers, depending on the balance among type and size of message, security, and technology available, may memorize messages, carry audio or video recordings, or hand-carry computer media.
[[Image:T-Cell-1.png|thumb|Core group and infrastructure cells; military cells in training]]

"These cells are socially embedded (less so than the core group, however), structurally embedded, functionally embedded (they are specialized into a domain), and knowledge base-specific (there does not seem to be a great deal of cross-training, or lateral mobility in the organization). Such cells are probably subjected to a mixture of positive and negative control ("do this, do these sorts of things, don’t do that")."&lt;ref name=Sleepers /&gt;

{| class="wikitable"
&lt;caption&gt;Core Structure of Non-National Group&lt;/caption&gt;
|-
! Member
! Infrastructure commanded
|-
| Richard
| Finance
|-
| Anton
| Military training/operations 1
|-
| Hassan
| Military training/operations 2
|-
| David
| Transportation
|-
| Kim
| Communications and propaganda
|}

The leaders of military cells are responsible for training them, and, when an operation is scheduled, selecting the operational commander, giving him the basic objective and arranging whatever support is needed, and then release him from tight control to execute the meeting. Depending on the specific case, the military leaders might have direct, possibly one-way, communications with their cells, or they might have to give Kim the messages to be transmitted, by means that Anton and Hassan have no need to know.

Note that Anton does not have a direct connection to Kim. Under normal circumstances, he sacrifices efficiency for security, by passing communications requests through Hassan. The security structure also means that Hassan does not know the members of Anton's cells, and Kim may know only ways to communicate with them but not their identity.

Kim operates two systems of cells, one for secure communications and one for propaganda. To send out a propaganda message, Osama must pass it to Kim. If Kim were compromised, the core group might have significant problems with any sort of outside communications.

Terrorist networks do not match cleanly to other cell systems that regularly report to a headquarters. The apparent al-Qaeda methodology of letting operational cells decide on their final dates and means of attack exhibit an operational pattern, but not a periodicity that could easily be used for an [[Intelligence analysis management#Indications &amp; warning checklists|indications checklist]] appropriate for a warning center. Such lists depend on seeing a local pattern to give a specific warning.&lt;ref name=Vos&gt;{{cite web
 | title = Modeling Terrorist Networks - Complex Systems at the Mid-Range
 | first1 = Philip Vos
 | last1 = Fellman
 | first2 = Roxana
 | last2 = Wright
 | url = http://www.psych.lse.ac.uk/complexity/Conference/FellmanWright.pdf
 |format=PDF| accessdate = 2007-11-02
}}&lt;/ref&gt;

Note that Hassan has two subordinates that have not yet established operational cells. These subordinates can be considered '''sleepers''', but not necessarily with a sleeper cell.

===Operational cells===
For each mission are created one or more operational cells. If the al-Qaeda signature of multiple concurrent attacks is used, there may be an operational cell for each target location. It will depend on the operation if they will need any support cells in the operational area. For example, it may be more secure to have a local cell build bombs, which will be delivered by cells coming from outside the area.

"Operational cells are not created, but instead 'seeded' utilizing individuals spotted or that request assistance (both groups are 'vetted' by being trained under the observation of the core group, which dramatically restricts the opportunity for passing off walk-ins under false flag). Categorization of operational cells appears to be by capabilities, region, and then task/operation. Operational cells are composed of members whose worldview has been firmly tested—necessary to front-load, because such cells are dispersed back to their own local control (or negative control—proscribed behavior—with positive control only coming in the form of contact for synchronization or support)."&lt;ref name=Sleepers /&gt;

If operational cells routinely are "released" ''curved dotted lines on link to military cells'' to select their final operational parameters, they use a different paradigm than governmental clandestine or covert operations. On a number of cases, US special operations forces had to wait for Presidential authorization to make an attack, or even move to staging areas. Admittedly, a country would have to face the consequences of an inappropriate attack, so it may tend to be overcautious, where a terror network would merely shrug at the world being upset. Assuming that the al-Qaeda operational technique is not to use positive control, their operations may be more random, but also more unpredictable for counterterror forces. If their cells truly need constant control, there are communications links that might be detected by SIGINT, and if their command can be disrupted, the field units could not function. Since there is fairly little downside for terrorists to attack out of synchronization with other activities, the lack of positive control becomes a strength of their approach to cell organization.
[[Image:T-Cell-2.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

The operational cells need to have continuous internal communication; there is a commander, who may be in touch with infrastructure cells or, less likely from a security standpoint with the core group.

Al-Qaeda's approach, which even differs from that of earlier terrorist organizations, may be very viable for their goals:

* Cells are redundant and distributed, making them difficult to ‘roll up’
* Cells are coordinated, not under "command &amp; control"—this autonomy and local control makes them flexible, and enhances security
* Trust and comcon internally to the cell provide redundancy of potential command (a failure of Palestinian operations in the past), and well as a shared knowledgebase (which may mean, over time, that ‘cross training’ emerges inside a cell, providing redundancy of most critical skills and knowledge).&lt;ref name=Sleepers /&gt;

===Indirect support networks===
In the above graphic, note the indirect support network controlled by Richard's subcell.

"While Al-Qaida has elements of the organization designed to support the structure, but such elements are insufficient in meeting the needs of such an organization, and for security reasons there would be redundant and secondary-/tertiary-networks that are unaware of their connection to Al-Qaida. These networks, primarily related to fundraising and financial activities, as well as technology providers, are in a ‘use’ relationship with Al-Qaida—managed through cut-outs or individuals that do not inform them of the nature of activities, and that may have a cover pretext sufficient to deflect questions or inquiry."&lt;ref name=Sleepers /&gt;

===A possible countermeasure===
In 2002, ''U.S. News &amp; World Report'' said that American intelligence is beginning to acquire a sufficiently critical mass of intelligence on al-Qaida indicating, "Once thought nearly impossible to penetrate, al Qaeda is proving no tougher a target than the KGB or the Mafia--closed societies that took the U.S. government years to get inside. "We're getting names, the different camps they trained at, the hierarchy, the infighting," says an intelligence official. "It's very promising."&lt;ref name=Kaplan2002&gt;{{Cite journal
 | title = Run and Gun: Al Qaeda arrests and intelligence hauls bring new energy to the war on terrorism
 | first = David E. | last = Kaplan
 | date = 22 September 2002
 | journal = U.S. News &amp; World Report
 | url = http://www.usnews.com/usnews/news/articles/020930/archive_022824.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; The report also said that the collected data has allowed the recruiting of informants.

Writing in the U.S. Army journal ''Military Review'', David W. Pendall  suggested that a "catch-and-release program for suspected operatives might create reluctance or distrust in such suspects and prevent them from further acts or, perhaps more important, create distrust in the cell leaders of these individuals in the future." The author noted the press release describing Ramzi Binalshib's cooperation with the United States "are sure to prevent reentry into a terrorist cell as a trusted member and most likely limits the further trust and assignments of close cell associates still at large. The captor would determine when to name names and when to remain silent."&lt;ref name=Pendall2004&gt;{{Cite journal
 | date = January–February 2004
 | journal = Military Review
 | url = http://calldp.leavenworth.army.mil
 | first = David W. | last = Pendall
 | title =Effects-Based Operations and the Exercise of National Power
 | publisher = [[United States Army Combined Arms Center]]
 | postscript = &lt;!--None--&gt;
}}  Find the article by going through the Military Review directories&lt;/ref&gt; Indeed, once intelligence learns the name and characteristics of an at-large adversary, as well as some sensitive information that would plausibly be known to him, a news release could be issued to talk about his cooperation. Such a method could not be used too often, but, used carefully, could disturb the critical trust networks. The greatest uncertainty might be associated with throwing doubt onto a key member of an operational cell that has gone autonomous.

==See also==
* [[Leaderless resistance]]
* [[Lone wolf (terrorism)]]

==References==
{{reflist | 2}}

==External links==
* [http://theriskyshift.com/2012/06/an-introduction-to-terrorist-organisational-structures/ An Introduction To Terrorist Organisational Structures]

{{Intelligence cycle management}}

[[Category:Counter-intelligence]]
[[Category:Types of espionage]]
[[Category:Intelligence analysis]]
[[Category:Military intelligence]]
[[Category:Military tactics]]
[[Category:Secrecy]]
[[Category:Terrorism tactics]]

[http://www.cimacell.com/wiki/index.php?title=Structure Reachback Ops]</text>
    <sha1>fb5a1d844ca4bdb97864146cb93843feaf88a994</sha1>
  </revision>
  <revision>
    <id>93</id>
    <parentid>89</parentid>
    <timestamp>2015-12-27T20:08:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[Clandestine cell system]] to [[Cell system]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39486" xml:space="preserve">__NOEDITSECTION__

{{for|the general use of a cellular structure by an organization, such as by a business|Cellular organization (disambiguation)}}
{{redirect|Sleeper cell}}
{{Use dmy dates|date=July 2011}}
{{multiple issues|
{{Essay-like|date=July 2011}}
{{POV|date=September 2012}}
{{Original research|date=January 2015}}
{{cleanup|reason=Poorly written, poorly referenced, marked essay-like (mostly user Hcberkowitz's edits; see page history) and POV issues and generally underlinked|date=January 2015}}
{{cleanup-rewrite|date=January 2015}}
{{Expert-subject|date=January 2015}}
}}

{{terrorism}}
A '''clandestine cell''' structure is a method for organizing a group of people like [[French resistance|resistance]] fighters or terrorists in such a way that it can more effectively resist penetration by an opposing organization (e.g., a law enforcement organization). In a cell structure, each small group of people in the cell only know the identities of the people in their cell; as such, if a cell member is apprehended and interrogated, he or she will not know the identities of the higher-ranking individuals in the organization. Depending on the group's [[philosophy]], its operational area, the communications technologies available, and the nature of the mission, it can range from a strict hierarchy to an extremely distributed organization. It is also a method used by [[organized crime|criminal organizations]], [[undercover]] operatives, and unconventional warfare (UW) units led by [[special forces]]. Historically, clandestine organizations have avoided electronic communications, because [[signals intelligence]] is a strength of conventional militaries and counterintelligence organizations.{{citation needed|date=August 2012}}

In the context of [[tradecraft]], [[covert operation|covert]] and [[clandestine operation|clandestine]] are not synonymous. As noted in the definition (which has been used by the United States and NATO since World War II) in a covert operation the identity of the sponsor is concealed, while in a clandestine operation the operation itself is concealed. Put differently, clandestine means "hidden", while covert means "deniable". The adversary is aware that a covert activity is happening, but does not know who is doing it, and certainly not their sponsorship. Clandestine activities, however, if successful, are completely unknown to the adversary, and their function, such as espionage, would be neutralized if there was any awareness of the activity.

A '''sleeper cell''' refers to a cell, or isolated grouping of [[sleeper agent]]s that lies dormant until it receives orders or decides to act.

==History==

=== Provisional Irish Republican Army===
As opposed to the [[French Resistance]], the modern [[Provisional Irish Republican Army]] (PIRA) has a history going back to Irish revolutionary forces in the early 20th century, but has little external control.  Its doctrine and organization have changed over time, given factors such as the independence of 26 of Ireland's 32 counties, the continued British control of Northern Ireland and the simple passage of time and changes in contemporary thinking and technology.&lt;ref name=Leahy&gt;{{cite web
 | url = http://cgsc.cdmhost.com/cgi-bin/showfile.exe?CISOROOT=/p4013coll2&amp;CISOPTR=386&amp;filename=387.pdf
 |format=PDF| author = Leahy, Kevin C.
 | year = 2005
 | title = The Impact of Technology on the Command, Control, and Organizational Structure of Insurgent Groups
 | accessdate=2007-12-04
}}&lt;/ref&gt;

Officially, the PIRA is hierarchical, but, especially as British security forces became more effective, changed to a semiautonomous model for its operational and certain of its support cells (e.g., transportation, intelligence, cover and security).&lt;ref name=GreenBook&gt;{{cite web
 | url = https://web.archive.org/web/20110606012137/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html
 | author = Irish Republican Army
 | title = The Green Book
 | accessdate=2007-12-04
|archiveurl=https://web.archive.org/web/20070616132240/http://uk.geocities.com/oglaigh_na_heireann32/THE_GREEN_BOOK.html|archivedate=2007-06-16}}&lt;/ref&gt; Its leadership sees itself as guiding and consensus-building. The lowest-level cells, typically of 2-5 people, tend to be built by people with an existing personal relationship. British counterinsurgents could fairly easily understand the command structure, but not the workings of the operational cells.

The IRA has an extensive network of inactive or sleeper cells, so new ''ad hoc'' organizations may appear for any specific operation.

===World War II French Resistance===
In World War II, [[Operation Jedburgh]] teams parachuted into occupied France to lead unconventional warfare units.&lt;ref name=Hall&gt;{{cite book
 | author = Hall, Roger
 | title = You're Stepping on my Cloak and Dagger
 | publisher = Bantam Books
 | year =1964
}}&lt;/ref&gt;&lt;ref name=SOETO&gt;{{cite book
 | chapterurl = http://www.history.army.mil/books/wwii/70-42/70-423.htm
 | chapter = Chapter 3: Special Operations in the European Theater
 | publisher = [[United States Army Center of Military History]]
| url = http://www.history.army.mil/books/wwii/70-42/70-42c.htm
| title = U.S. Army Special Operations in World War II
| first = David W.
| last = Hogan
| id = CMH Pub 70-42
|year = 1992
| location = Washington, D.C.
}}&lt;/ref&gt; They would be composed of two officers, one American or British, and the other French, the latter preferably from the area into which they landed. The third member of the team was a radio operator.

Especially through the French member, they would contact trusted individuals in the area of operation, and ask them to recruit a team of trusted subordinates (i.e., a subcell). If the team mission were sabotage, reconnaissance, or espionage, there was no need to meet in large units. If the team was to carry out direct action, often an unwise mission unless an appreciable number of the locals had military experience, it would be necessary to assemble into units for combat. Even then, the hideouts of the leadership were known only to subcell leaders. The legitimacy of the Jedburgh team came from its known affiliation with Allied powers, and it was a structure more appropriate for UW than for truly clandestine operations.

===National Front for the Liberation of South Vietnam===
Also known as the [[Viet Cong]], this organization grew from earlier anticolonial groups fighting the French, as well as anti-Japanese guerillas during World War II.&lt;ref name=VietCong&gt;{{cite book
 | author = Pike, Douglas
 | title = Viet Cong: Organization and Technique of the National Liberation Front of South Vietnam
 | publisher = MIT Press
 | year = 1970
}}&lt;/ref&gt;
Its command, control, and communication techniques derived from the experiences of these earlier insurgent groups. The group had extensive support from North Vietnam, and, indirectly, from the Soviet Union. It had parallel political and military structures, often overlapping. See [[Viet Cong and PAVN strategy and tactics]].
[[Image:Vcnvastructure4rev.jpg|thumb|right |A dual, but sometimes overlapping, Party and Military structure was top-down]]
The lowest level consisted of three-person cells who operated quite closely, and engaging in the sort of [[self-criticism]] common, as a bonding method, to Communist organizations.{{Citation needed|date=June 2014}}

==Parallel organizations==
The NLF and PIRA, as well as other movements, have chosen to have parallel political and military organizations. In the case of the NLF, other than some individuals with sanctuary in North Vietnam, the political organization could not be overt during the [[Vietnam War]]. After the war ended, surviving NLF officials held high office.

In the case of the PIRA, its political wing, [[Sinn Féin]], became increasingly overt, and then a full participant in politics. [[Hamas]] and [[Hezbollah]] also have variants of overt political/social service and covert military wings.

The overt political/social–covert military split avoided the inflexibility of a completely secret organization. Once an active insurgency began, the secrecy {{clarify span|could limit|date=January 2015}}&lt;!-- what? --&gt; freedom of action, distort information about goals and ideals, and restrict communication within the insurgency.&lt;ref name=FM3-24&gt;{{cite web
 | title = FM 3-24: Counterinsurgency
 | author = US Department of the Army
 |date=December 2006
 | url = https://fas.org/irp/doddir/army/fm3-24.pdf
|format=PDF}}&lt;/ref&gt; In a split organization, the public issues can be addressed overtly, while military actions were kept covert and intelligence functions stay clandestine.

==External support==
Many cell systems still receive, with due attention to security, support from the outside. This can range from leaders, trainers and supplies (such as the Jedburgh assistance to the French Resistance), or a safe haven for overt activities (such as the NLF spokesmen in Hanoi).

External support need not be overt. Certain Shi'a groups in Iraq, for example, do receive assistance from Iran{{Citation needed|date=March 2009}}, but this is not a public position of the government of Iran, and may even be limited to factions of that government.  Early US support to the Afghan Northern Alliance against the Taliban used clandestine operators from both the [[CIA]] and [[United States Army Special Forces]]. As the latter conflict escalated, the US participation became overt.

Note that both [[unconventional warfare]] (UW) (guerrilla operations) and [[foreign internal defense]] (FID) (counterinsurgency) may be covert and use cellular organization.

In a covert FID mission, only selected host nation (HN) leaders are aware of the foreign support organization. Under [[Operation White Star]], US personnel gave covert FID assistance to the Royal Lao Army starting in 1959, became overt in 1961, and ceased operations in 1962.

==Models of insurgency and associated cell characteristics==
While different kinds of insurgency differ in where they place clandestine or covert cells, when certain types of insurgency grow in power, the cell system is deemphasized. Cells still may be used for leadership security, but, if overt violence by organized units becomes significant, cells are less important. In Mao's three-stage doctrine,&lt;ref name=Mao1967&gt;{{cite book
 | title = On Protracted War
 | author = Mao,  Zedong | authorlink = Mao Zedong
 | year = 1967
 | publisher = Foreign Language Press, Beijing
}}&lt;/ref&gt; cells are still useful in Phase II to give cover to part-time guerillas, but, as the insurgency creates full-time military units in Phase III, the main units are the focus, not the cells. The [[Eighth Route Army]] did not run on a cell model.

When considering where cells exist with respect to the existing government, the type of insurgency needs to be considered. One US Army reference was Field Manual 100-20, which has been superseded by FM3-07.&lt;ref name=FM3-07&gt;{{cite web
 | title = FM 3-07 (formerly FM 100-20): Stability Operations and Support Operations
 | date = 20 February 2003
 | author = US Department of the Army
 | url = https://atiam.train.army.mil/soldierPortal/atia/adlsc/view/altfmt/9630-1
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; Drawing on this work, Nyberg (a [[United States Marine Corps]] officer) extended the ideas to describe four types of cell system, although his descriptions also encompass types of insurgencies that the cell system supports.&lt;ref name=Nyberg&gt;{{Cite journal
 | title = Insurgency: The Unsolved Mystery
 | first = Eric N. | last = Nyberg
 | publisher = US Marine Corps University Command and Staff College
 | year = 1991
 | url = http://www.globalsecurity.org/military/library/report/1991/NEN.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt;  At present, there is a new type associated with transnational terrorist insurgencies.

# Traditional: the slowest to form, this reflects a principally indigenous insurgency, initially with limited goals. It is more secure than others, as it tends to grow from people with social, cultural or family ties. The insurgents resent a government that has failed to recognize  tribal, racial, religious or linguistic groups "who perceive that the government has denied their rights and interests and work to establish or restore them. They seldom seek to overthrow the government or control the whole society; however, they frequently attempt to withdraw from government control through autonomy or semiautonomy." The Mujahideen in Afghanistan and the Kurdish revolt in Iraq illustrate the traditional pattern of insurgency. [[al-Qaeda]] generally operates in this mode, but if they become strong enough in a given area, they may change to the mass-oriented form.
# Subversive: Usually driven by an organization that contains at least some of the governing elite, some being sympathizers already in place, and others who penetrate the government. When they use violence, it has a specific purpose, such as coercing voters, intimidating officials, and disrupting and discrediting the government. Typically, there is a political arm (such as  [[Sinn Féin]] or the [[Viet Cong|National Liberation Front]]) that directs the military in planning carefully coordinated violence. "Employment of violence is designed to show the system to be incompetent and to provoke the government to an excessively violent response which further undermines its legitimacy." The [[Nazi]] rise to power, in the 1930s, is another example of subversion. Nazi members of parliament and street fighters were hardly clandestine, but the overall plan of the Nazi leadership to gain control of the nation was hidden. "A subversive insurgency is suited to a more permissive political environment which allows the insurgents to use both legal and illegal methods to accomplish their goals. Effective government resistance may convert this to a critical-cell model.
# Critical-cell: Critical cell is useful when the political climate becomes less permissive than one that allowed shadow cells. While other cell types try to form intelligence cells within the government, this type sets up "[[Continuity of government|shadow government]]" cells that can seize power once the system is destroyed both by external means and the internal subversion. This model fits the classic [[coup d'etat]],&lt;ref name=Luttwak&gt;{{cite book
 | title = Coup d'etat: A Practical Handbook
 | year = 1968
 | author = Luttwak, Edward | authorlink = Edward Luttwak
 | publisher = Harvard University Press
}}&lt;/ref&gt; and often tries to minimize violence. Variants include the [[Sandinista]] takeover of an existing government weakened by external popular revolution. "Insurgents also seek to infiltrate the government's institutions, but their object is to destroy the system from within." Clandestine cells form inside the government. "The use of violence remains covert until the government is so weakened that the insurgency's superior organization seizes power, supported by the armed force. One variation of this pattern is when the insurgent leadership permits the popular revolution to destroy the existing government, then emerges to direct the formation of a new government. Another variation is seen in the [[Cuba]]n revolution&lt;ref name=Guevara&gt;{{cite book
 | author = Guevara, Ernesto "Che"
 | title = On Guerilla Warfare
 | publisher = Praeger
 | year = 1961
}}&lt;/ref&gt; and is referred to as the foco (or Cuban model) insurgency. This model involves a single, armed cell which emerges in the midst of degenerating government legitimacy and becomes the nucleus around which mass popular support rallies.  The insurgents use this support to establish control and erect new institutions."
# Mass-oriented: where the subversive and covert-cell systems work from within the government, the mass-oriented builds a government completely outside the existing one, with the intention of replacing it. Such "insurgents patiently construct a base of passive and active political supporters, while simultaneously building a large armed element of guerrilla and regular forces.  They plan a protracted campaign of increasing violence to destroy the government and its institutions from the outside.  They have a well-developed ideology and carefully determine their objectives.  They are highly organized and effectively use propaganda and guerrilla action to mobilize forces for a direct political and military challenge to the government." The revolution that produced the [[Peoples' Republic of China]], the [[American Revolution]], and the [[Shining Path]] insurgency in Peru are examples of the mass-oriented model. Once established, this type of insurgency is extremely difficult to defeat because of its great depth of organization.

==Classic models for cell system operations==
Different kinds of cell organizations have been used for different purposes. This section focuses on clandestine cells, as would be used for [[espionage]], [[sabotage]], or the organization for [[unconventional warfare]]. When unconventional warfare starts using overt units, the cell system tends to be used only for sensitive leadership and intelligence roles.&lt;ref name=Mao1967 /&gt; The examples here will use [[CIA cryptonym]]s as a naming convention used to identify members of the cell system. Cryptonyms begin with a two-letter country or subject name (e.g., AL), followed with an arbitrary word. It is considered elegant to have the code merge with the other letters to form a pronounceable word.

===Operations under official cover===
Station BERRY operates, for country B, in target country BE. It has three case officers and several support officers. Espionage operation run by case officers under diplomatic cover, they would have to with the basic recruiting methods described in this article. Case officer BETTY runs the local agents BEN and BEATLE. Case officer BESSIE runs BENSON and BEAGLE.
[[Image:Wdip-Cell-0.png|thumb|Representative diplomatic-cover station and networks]]

Some recruits, due to the sensitivity of their position or their personalities not being appropriate for cell leadership, might not enter cells but be run as singletons, perhaps by other than the recruiting case officer. Asset BARD is a different sort of highly sensitive singleton, who is a joint asset of the country B, and the country identified by prefix AR. ARNOLD is a case officer from the country AR embassy, who knows only the case officer BERTRAM and the security officer BEST. ARNOLD does not know the station chief of BERRY or any of its other personnel. Other than BELL and BEST, the Station personnel only know BERTRAM as someone authorized to be in the Station, and who is known for his piano playing at embassy parties. He is covered as Cultural Attache, in a country that has very few pianos. Only the personnel involved with BARD know that ARNOLD is other than another friendly diplomat.

In contrast, BESSIE and BETTY know one another, and procedures exist for their taking over each other's assets in the event one of the two is disabled.

Some recruits, however, would be qualified to recruit their own subcell, as BEATLE has done. BESSIE knows the identity of BEATLE-1 and BEATLE-2, since he had them checked by headquarters counterintelligence before they were recruited. Note that a cryptonym does not imply anything about its  designee, such as gender.

===Clandestine presence===
The diagram of "initial team presence" shows that two teams, ALAN and ALICE, have successfully entered an area of operation, the country coded AL, but are only aware of a pool of potential recruits, and have not yet actually recruited anyone. They communicate with one another only through headquarters, so compromise of one team will not affect the other.
[[Image:Wnoc-Cell-0.png|thumb|left |Initial team presence by 2 separate clandestine teams with no official cover]]

Assume that in team ALAN, ALASTAIR is one of the officers with local contacts, might recruit two cell leaders, ALPINE and ALTITUDE. The other local officer in the team, ALBERT, recruits ALLOVER.  When ALPINE recruited two subcell members, they would be referred to as ALPINE-1 and ALPINE-2.

ALPINE and ALTITUDE only know how to reach ALASTAIR, but they are aware of at least some of other team members' identity should ALASTAIR be unavailable, and they would accept a message from ALBERT. Most often, the identity (and location) of the radio operator may not be shared. ALPINE and ALTITUDE, however, do not know one another. They do not know any of the members of team ALICE.

The legitimacy of the subcell structure came from the recruitment process, originally by the case officer and then by the cell leaders. Sometimes, the cell leader would propose subcell member names to the case officer, so the case officer could have a headquarters name check run before bringing the individual into the subcell. In principle, however, the subcell members would know ALPINE, and sometimes the other members of the ALPINE cell if they needed to work together; if ALPINE-1 and ALPINE-2 had independent assignments, they might not know each other. ALPINE-1 and ALPINE-2 certainly would not know ALASTAIR or anyone in the ALTITUDE or ALLOVER cells.
[[Image:Wnoc-Cell-1.png|thumb|Clandestine teams have built initial subcells]]

As the networks grow, a subcell leader might create his own cell, so ALPINE-2 might become the leader of the ALIMONY cell.

===Fault-tolerant cellular structures===
Modern communications theory has introduced methods to increase fault tolerance in cell organizations. In the past, if cell members only knew the cell leader, and the leader was neutralized, the cell was cut off from the rest of the organization. Game theory and graph theory have been applied to the study of optimal covert network design (see Lindelauf, R.H.A. et al. 2009. The influence of secrecy on the communication structure of covert networks. Social Networks 31: 126-137).

If a traditional cell had independent communications with the foreign support organization, headquarters might be able to arrange its reconnection. Another method is to have impersonal communications "side links" between cells, such as a pair of [[dead drop]]s, one for Team ALAN to leave "lost contact" messages to be retrieved by Team ALICE, and another dead drop for Team ALICE to leave messages for Team ALAN.

These links, to be used only on losing contact, do not guarantee a contact. When a team finds a message in its emergency drop, it might do no more than send an alert message to headquarters. Headquarters might determine, through [[SIGINT]] or other sources, that the enemy had captured the leadership and the entire team, and order the other team not to attempt contact. If headquarters can have reasonable confidence that there is a communications failure or partial compromise, it might send a new contact to the survivors.

When the cut-off team has electronic communications, such as the Internet, it has a much better chance of eluding surveillance and getting emergency instructions than by using a dead drop that can be under physical surveillance.

==Non-traditional models, exemplified by al-Qaeda==
Due to cultural differences, assuming the ''al-Qaeda Training Manual''&lt;ref name=AQTM&gt;{{cite web
 | url = https://fas.org/irp/world/para/aqmanual.pdf
 |format=PDF| title = al-Qaeda training manual
 | publisher = US Southern District Court, US New York City Attorney's Office, entered as evidence in Africa embassy bombings
}}&lt;/ref&gt; is authentic, eastern cell structures may differ from the Western mode. "Al-Qaida's minimal core group, only accounting for the leadership, can also be viewed topologically as a ring or chain network, with each leader/node heading their own particular hierarchy.

"Such networks function by having their sub-networks provide information and other forms of support (the ‘many-to-one’ model), while the core group supplies ‘truth’ and decisions/directions (the ‘one-to-many’ model). Trust and personal relationships are an essential part of the Al-Qaida network (a limiting factor, even while it provides enhanced security). Even while cell members are trained as ‘replaceable’ units, ‘vetting’ of members occurs during the invited training period under the observation of the core group.&lt;ref name=Sleepers&gt;{{cite web
 | url = http://www.metatempo.com/huntingthesleepers.pdf
 |format=PDF| title = Hunting the Sleepers: Tracking al-Qaida's Covert Operatives
 | date = 2001-12-31
 | author = Decision Support Systems, Inc.
 | accessdate = 2007-11-17
}}&lt;/ref&gt;

Cells of this structure are built outwards, from an internal leadership core. Superficially, this might be likened to a Western cell structure that emanates from a headquarters, but the Western centrality is bureaucratic, while structures in other non-western cultures builds on close personal relationships, often built over years, perhaps involving family or other in-group linkages. Such in-groups are thus extremely hard to infiltrate; infiltration has a serious chance only outside the in-group. Still, it may be possible for an in-group to be compromised through [[COMINT]] or, in rare cases, by compromising a member.

The core group is logically a ring, but is superimposed on an inner hub-and-spoke structure of ideological authority. Each member of the core forms another hub and spoke system (see [[#Infrastructure cells|infrastructure cells]]), the spokes leading to infrastructure cells under the supervision of the core group member, and possibly to operational groups which the headquarters support. Note that in this organization, there is a point at which the operational cell becomes autonomous of the core. Members surviving the operation may rejoin at various points.
[[Image:T-Cell-0.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

Osama, in this model, has the main responsibility of commanding the organization and being the spokesman on propaganda video and audio messages distributed by the propaganda cell. The other members of the core each command one or more infrastructure cells.

While the tight coupling enhances security, it can limit flexibility and the ability to scale the organization. This in-group, while sharing tight cultural and ideological values, is not committed to a bureaucratic process.

"Members of the core group are under what could be termed 'positive control'—long relationships
and similar mindsets make 'control' not so much of an issue, but there are distinct roles, and position (structural, financial, spiritual) determines authority, thus making the core group a hierarchy topologically.&lt;ref name=Sleepers /&gt;

In the first example of the core, each member knows how to reach two other members, and also knows the member(s) he considers his ideological superior. Solid lines show basic communication, dotted red arrows show the first level of ideological respect, and dotted blue arrows show a second level of ideological respect.

If Osama, the most respected, died, the core would reconstitute itself. While different members have an individual ideological guide, and these are not the same for all members, the core would reconstitute itself with Richard as most respected.

Assume there are no losses, and Osama can be reached directly only by members of the core group. Members of outer cells and support systems might know him only as "the Commander", or, as in the actual case of al-Qaeda, Osama bin Laden's face is recognizable worldwide, but only a few people know where he was or even how to contact him.

===Infrastructure cells===
Any clandestine or covert service, especially a non-national one, needs a variety of technical and administrative functions. Some of these services include:&lt;ref name=Sleepers /&gt;

# Forged documents and counterfeit currency
# Apartments and hiding places
# Communication means
# Transportation means
# Information
# Arms and ammunition
# Transport

Other functions include psychological operations, training, and finance.

A national intelligence service&lt;ref name=CIAsupport&gt;{{cite web
 | url = https://www.cia.gov/offices-of-cia/mission-support/who-we-are.html
 | author = US Central Intelligence Agency
 | title = Support to Mission: Who We Are
 | accessdate = 2007-11-19
}}&lt;/ref&gt;
has a support organization to deal with services such as finance, logistics, facilities (e.g., [[#Safehouses and Other Meeting Places|safehouses]]), information technology, communications, training, weapons and explosives, medical services, etc. Transportation alone is a huge function, including the need to buy tickets without drawing suspicion, and, where appropriate, using private vehicles. Finance includes the need to transfer money without coming under the suspicion of financial security organizations.

Some of these functions, such as finance, are far harder to operate in remote areas, such as the [[FATA]] of [[Pakistan]], than in cities with large numbers of official and unofficial financial institutions, and the communications to support them. If the financial office is distant from the remote headquarters, there is a need for [[couriers]], who must be trusted to some extent, but they may not know the contents of their messages or the actual identity of sender and/or receiver. The couriers, depending on the balance among type and size of message, security, and technology available, may memorize messages, carry audio or video recordings, or hand-carry computer media.
[[Image:T-Cell-1.png|thumb|Core group and infrastructure cells; military cells in training]]

"These cells are socially embedded (less so than the core group, however), structurally embedded, functionally embedded (they are specialized into a domain), and knowledge base-specific (there does not seem to be a great deal of cross-training, or lateral mobility in the organization). Such cells are probably subjected to a mixture of positive and negative control ("do this, do these sorts of things, don’t do that")."&lt;ref name=Sleepers /&gt;

{| class="wikitable"
&lt;caption&gt;Core Structure of Non-National Group&lt;/caption&gt;
|-
! Member
! Infrastructure commanded
|-
| Richard
| Finance
|-
| Anton
| Military training/operations 1
|-
| Hassan
| Military training/operations 2
|-
| David
| Transportation
|-
| Kim
| Communications and propaganda
|}

The leaders of military cells are responsible for training them, and, when an operation is scheduled, selecting the operational commander, giving him the basic objective and arranging whatever support is needed, and then release him from tight control to execute the meeting. Depending on the specific case, the military leaders might have direct, possibly one-way, communications with their cells, or they might have to give Kim the messages to be transmitted, by means that Anton and Hassan have no need to know.

Note that Anton does not have a direct connection to Kim. Under normal circumstances, he sacrifices efficiency for security, by passing communications requests through Hassan. The security structure also means that Hassan does not know the members of Anton's cells, and Kim may know only ways to communicate with them but not their identity.

Kim operates two systems of cells, one for secure communications and one for propaganda. To send out a propaganda message, Osama must pass it to Kim. If Kim were compromised, the core group might have significant problems with any sort of outside communications.

Terrorist networks do not match cleanly to other cell systems that regularly report to a headquarters. The apparent al-Qaeda methodology of letting operational cells decide on their final dates and means of attack exhibit an operational pattern, but not a periodicity that could easily be used for an [[Intelligence analysis management#Indications &amp; warning checklists|indications checklist]] appropriate for a warning center. Such lists depend on seeing a local pattern to give a specific warning.&lt;ref name=Vos&gt;{{cite web
 | title = Modeling Terrorist Networks - Complex Systems at the Mid-Range
 | first1 = Philip Vos
 | last1 = Fellman
 | first2 = Roxana
 | last2 = Wright
 | url = http://www.psych.lse.ac.uk/complexity/Conference/FellmanWright.pdf
 |format=PDF| accessdate = 2007-11-02
}}&lt;/ref&gt;

Note that Hassan has two subordinates that have not yet established operational cells. These subordinates can be considered '''sleepers''', but not necessarily with a sleeper cell.

===Operational cells===
For each mission are created one or more operational cells. If the al-Qaeda signature of multiple concurrent attacks is used, there may be an operational cell for each target location. It will depend on the operation if they will need any support cells in the operational area. For example, it may be more secure to have a local cell build bombs, which will be delivered by cells coming from outside the area.

"Operational cells are not created, but instead 'seeded' utilizing individuals spotted or that request assistance (both groups are 'vetted' by being trained under the observation of the core group, which dramatically restricts the opportunity for passing off walk-ins under false flag). Categorization of operational cells appears to be by capabilities, region, and then task/operation. Operational cells are composed of members whose worldview has been firmly tested—necessary to front-load, because such cells are dispersed back to their own local control (or negative control—proscribed behavior—with positive control only coming in the form of contact for synchronization or support)."&lt;ref name=Sleepers /&gt;

If operational cells routinely are "released" ''curved dotted lines on link to military cells'' to select their final operational parameters, they use a different paradigm than governmental clandestine or covert operations. On a number of cases, US special operations forces had to wait for Presidential authorization to make an attack, or even move to staging areas. Admittedly, a country would have to face the consequences of an inappropriate attack, so it may tend to be overcautious, where a terror network would merely shrug at the world being upset. Assuming that the al-Qaeda operational technique is not to use positive control, their operations may be more random, but also more unpredictable for counterterror forces. If their cells truly need constant control, there are communications links that might be detected by SIGINT, and if their command can be disrupted, the field units could not function. Since there is fairly little downside for terrorists to attack out of synchronization with other activities, the lack of positive control becomes a strength of their approach to cell organization.
[[Image:T-Cell-2.png|thumb|left |Core group, with contact ring and ideological hierarchy]]

The operational cells need to have continuous internal communication; there is a commander, who may be in touch with infrastructure cells or, less likely from a security standpoint with the core group.

Al-Qaeda's approach, which even differs from that of earlier terrorist organizations, may be very viable for their goals:

* Cells are redundant and distributed, making them difficult to ‘roll up’
* Cells are coordinated, not under "command &amp; control"—this autonomy and local control makes them flexible, and enhances security
* Trust and comcon internally to the cell provide redundancy of potential command (a failure of Palestinian operations in the past), and well as a shared knowledgebase (which may mean, over time, that ‘cross training’ emerges inside a cell, providing redundancy of most critical skills and knowledge).&lt;ref name=Sleepers /&gt;

===Indirect support networks===
In the above graphic, note the indirect support network controlled by Richard's subcell.

"While Al-Qaida has elements of the organization designed to support the structure, but such elements are insufficient in meeting the needs of such an organization, and for security reasons there would be redundant and secondary-/tertiary-networks that are unaware of their connection to Al-Qaida. These networks, primarily related to fundraising and financial activities, as well as technology providers, are in a ‘use’ relationship with Al-Qaida—managed through cut-outs or individuals that do not inform them of the nature of activities, and that may have a cover pretext sufficient to deflect questions or inquiry."&lt;ref name=Sleepers /&gt;

===A possible countermeasure===
In 2002, ''U.S. News &amp; World Report'' said that American intelligence is beginning to acquire a sufficiently critical mass of intelligence on al-Qaida indicating, "Once thought nearly impossible to penetrate, al Qaeda is proving no tougher a target than the KGB or the Mafia--closed societies that took the U.S. government years to get inside. "We're getting names, the different camps they trained at, the hierarchy, the infighting," says an intelligence official. "It's very promising."&lt;ref name=Kaplan2002&gt;{{Cite journal
 | title = Run and Gun: Al Qaeda arrests and intelligence hauls bring new energy to the war on terrorism
 | first = David E. | last = Kaplan
 | date = 22 September 2002
 | journal = U.S. News &amp; World Report
 | url = http://www.usnews.com/usnews/news/articles/020930/archive_022824.htm
 | postscript = &lt;!--None--&gt;
}}&lt;/ref&gt; The report also said that the collected data has allowed the recruiting of informants.

Writing in the U.S. Army journal ''Military Review'', David W. Pendall  suggested that a "catch-and-release program for suspected operatives might create reluctance or distrust in such suspects and prevent them from further acts or, perhaps more important, create distrust in the cell leaders of these individuals in the future." The author noted the press release describing Ramzi Binalshib's cooperation with the United States "are sure to prevent reentry into a terrorist cell as a trusted member and most likely limits the further trust and assignments of close cell associates still at large. The captor would determine when to name names and when to remain silent."&lt;ref name=Pendall2004&gt;{{Cite journal
 | date = January–February 2004
 | journal = Military Review
 | url = http://calldp.leavenworth.army.mil
 | first = David W. | last = Pendall
 | title =Effects-Based Operations and the Exercise of National Power
 | publisher = [[United States Army Combined Arms Center]]
 | postscript = &lt;!--None--&gt;
}}  Find the article by going through the Military Review directories&lt;/ref&gt; Indeed, once intelligence learns the name and characteristics of an at-large adversary, as well as some sensitive information that would plausibly be known to him, a news release could be issued to talk about his cooperation. Such a method could not be used too often, but, used carefully, could disturb the critical trust networks. The greatest uncertainty might be associated with throwing doubt onto a key member of an operational cell that has gone autonomous.

==See also==
* [[Leaderless resistance]]
* [[Lone wolf (terrorism)]]

==References==
{{reflist | 2}}

==External links==
* [http://theriskyshift.com/2012/06/an-introduction-to-terrorist-organisational-structures/ An Introduction To Terrorist Organisational Structures]

{{Intelligence cycle management}}

[[Category:Counter-intelligence]]
[[Category:Types of espionage]]
[[Category:Intelligence analysis]]
[[Category:Military intelligence]]
[[Category:Military tactics]]
[[Category:Secrecy]]
[[Category:Terrorism tactics]]

[http://www.cimacell.com/wiki/index.php?title=Structure Reachback Ops]</text>
    <sha1>fb5a1d844ca4bdb97864146cb93843feaf88a994</sha1>
  </revision>
</page>
<page arvcontinue="20151224212631|43">
  <title>File:Vcnvastructure4rev.jpg</title>
  <ns>6</ns>
  <id>53</id>
  <revision>
    <id>90</id>
    <timestamp>2015-12-27T01:38:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>:Reachback Ops</title>
  <ns>3000</ns>
  <id>54</id>
  <revision>
    <id>94</id>
    <timestamp>2015-12-27T22:45:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;presentation name='Reachback Operations=","&gt;     Agenda,      Upcoming Events,      New Hires &lt;/presentation&gt;"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="110" xml:space="preserve">&lt;presentation name='Reachback Operations=","&gt;
    Agenda, 
    Upcoming Events, 
    New Hires
&lt;/presentation&gt;</text>
    <sha1>0ca54fd60e03bed1fafdcd57978676b867ba5c78</sha1>
  </revision>
  <revision>
    <id>95</id>
    <parentid>94</parentid>
    <timestamp>2015-12-27T22:45:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="121" xml:space="preserve">&lt;presentation name='Reachback Operations' delimiter=","&gt;
    Agenda, 
    Upcoming Events, 
    New Hires
&lt;/presentation&gt;</text>
    <sha1>ef425e633873cdef061e680c4b83178e4ed5ff38</sha1>
  </revision>
  <revision>
    <id>96</id>
    <parentid>95</parentid>
    <timestamp>2015-12-27T22:47:32Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="121" xml:space="preserve">&lt;presentation name='Reachback Operations' delimiter=","&gt;
    Support, 
    Capabilities, 
    Cell System
&lt;/presentation&gt;</text>
    <sha1>a3794fef2b6d4353ec88713e04184fbe2e51fd8a</sha1>
  </revision>
  <revision>
    <id>98</id>
    <parentid>96</parentid>
    <timestamp>2015-12-27T23:52:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="135" xml:space="preserve">&lt;presentation name='Reachback Operations' delimiter=","&gt;
    Overview,
    Support, 
    Capabilities, 
    Cell System
&lt;/presentation&gt;</text>
    <sha1>b8132b1b73058cae2f0c31146e148d2604698dbf</sha1>
  </revision>
  <revision>
    <id>100</id>
    <parentid>98</parentid>
    <timestamp>2015-12-27T23:59:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[Presenation:Reachback Ops]] to [[Presentation:Reachback Ops]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="135" xml:space="preserve">&lt;presentation name='Reachback Operations' delimiter=","&gt;
    Overview,
    Support, 
    Capabilities, 
    Cell System
&lt;/presentation&gt;</text>
    <sha1>b8132b1b73058cae2f0c31146e148d2604698dbf</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>Category:Indexed pages</title>
  <ns>14</ns>
  <id>55</id>
  <revision>
    <id>97</id>
    <timestamp>2015-12-27T23:47:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This is the Indexed pages category."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="35" xml:space="preserve">This is the Indexed pages category.</text>
    <sha1>15140b1cf0bf79e3f29c609d0d942a884787dff9</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>:Overview</title>
  <ns>3000</ns>
  <id>56</id>
  <revision>
    <id>99</id>
    <timestamp>2015-12-27T23:58:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Reachback"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9" xml:space="preserve">Reachback</text>
    <sha1>61532ea93d3e312ab301bf6345cf33cdede31212</sha1>
  </revision>
  <revision>
    <id>101</id>
    <parentid>99</parentid>
    <timestamp>2015-12-28T00:00:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[Overview]] to [[Presentation:Overview]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9" xml:space="preserve">Reachback</text>
    <sha1>61532ea93d3e312ab301bf6345cf33cdede31212</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>Reachback Operations</title>
  <ns>0</ns>
  <id>43</id>
  <revision>
    <id>102</id>
    <parentid>92</parentid>
    <timestamp>2015-12-28T10:05:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2422" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Situation Center&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;[[Early Warning Alert System]]&lt;/h2&gt;
|}

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;[[Situation Reports and Briefings]]&lt;/h2&gt;
|}

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;[[Early Warning and Alerts]]&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>7404fe888d6f77254ca11f42695078066d623990</sha1>
  </revision>
  <revision>
    <id>103</id>
    <parentid>102</parentid>
    <timestamp>2015-12-28T10:07:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* Areas of Interest */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1851" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Situation Center&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;[[Early Warning Alert System]]&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>72fef339715c5a525f667c24831c34c0b2d6f827</sha1>
  </revision>
  <revision>
    <id>104</id>
    <parentid>103</parentid>
    <timestamp>2015-12-28T10:09:30Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1851" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Joint Operations&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;[[Early Warning Alert System]]&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>13d45658ebf78e77d3e1c0d470ab5db75720f183</sha1>
  </revision>
  <revision>
    <id>105</id>
    <parentid>104</parentid>
    <timestamp>2015-12-28T10:15:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1844" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Framework&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;[[Early Warning Alert System]]&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>723cdf520a302bca481a2edc00046b8a70bd3344</sha1>
  </revision>
  <revision>
    <id>106</id>
    <parentid>105</parentid>
    <timestamp>2015-12-28T10:17:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1862" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Assurance Support Framework&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;[[Early Warning Alert System]]&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>83294f168b832399f1d7df0b7136784308b70d44</sha1>
  </revision>
  <revision>
    <id>107</id>
    <parentid>106</parentid>
    <timestamp>2015-12-28T10:22:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1858" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Architectural Framework&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;[[Early Warning Alert System]]&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>05d56ca0e790504d589ae2f1e469eb95abc645cc</sha1>
  </revision>
  <revision>
    <id>108</id>
    <parentid>107</parentid>
    <timestamp>2015-12-28T10:25:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* Areas of Interest */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1848" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Architectural Framework&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback capability&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>3a2453a968fb571ef4e0e9b911e0bfe88adbc5a4</sha1>
  </revision>
  <revision>
    <id>109</id>
    <parentid>108</parentid>
    <timestamp>2015-12-28T10:27:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* Areas of Interest */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2119" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Architectural Framework&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>b84ab4e910bc3e84b2073a71d7cce05633f8b5f7</sha1>
  </revision>
  <revision>
    <id>110</id>
    <parentid>109</parentid>
    <timestamp>2015-12-28T11:05:30Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2118" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Architectural Framework&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>830f21a1d1b577f54cb4f6ecd6ca5bf8829bd188</sha1>
  </revision>
  <revision>
    <id>111</id>
    <parentid>110</parentid>
    <timestamp>2015-12-28T11:13:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2668" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Architectural Framework&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Capabilities
&lt;/h2&gt;

|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Assurance&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}


{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}


= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>c95e4f7ad82d6c5f245c2dee2b000c739900586f</sha1>
  </revision>
  <revision>
    <id>112</id>
    <parentid>111</parentid>
    <timestamp>2015-12-28T11:15:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2676" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Architectural Framework&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Capabilities
&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Mission Assurance&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Operational Support&lt;/h2&gt;
|}


{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}


= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Plans and Policy =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>7b80b66cf8f482dc76dafb5a06c288b1c856b368</sha1>
  </revision>
  <revision>
    <id>113</id>
    <parentid>112</parentid>
    <timestamp>2015-12-28T11:16:46Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2678" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Architectural Framework&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Capabilities
&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Mission Assurance&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Operational Support&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Policy and Structuring =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>790668b98498751e914ca0a4b25fe78afa27e4b3</sha1>
  </revision>
  <revision>
    <id>114</id>
    <parentid>113</parentid>
    <timestamp>2015-12-28T11:18:03Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2475" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Architectural Framework&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Mission Assurance&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Operational Support&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Policy and Structuring =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>7459cbdbe779a0a9f6a9fe13e8019f59edf7a220</sha1>
  </revision>
  <revision>
    <id>115</id>
    <parentid>114</parentid>
    <timestamp>2015-12-28T14:01:46Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2483" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Operational and Mission Support&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Mission Assurance&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Operational Support&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Policy and Structuring =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>3032128644768cb4dee9e8280f83b3ec402cc2ba</sha1>
  </revision>
  <revision>
    <id>116</id>
    <parentid>115</parentid>
    <timestamp>2015-12-28T14:03:39Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2484" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Operations and Mission Assurance&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Mission Assurance&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Operational Support&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Policy and Structuring =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>21a705f882b4f7de5b7780fe193b69911c854ff4</sha1>
  </revision>
  <revision>
    <id>117</id>
    <parentid>116</parentid>
    <timestamp>2015-12-28T14:08:12Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2473" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Innovative Servicea 
&lt;/div&gt;
|}
|}

= Areas of Interest =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}

= Support =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Mission Assurance&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Operational Support&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}

= Electronic Library =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Policy and Structuring =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>51575bf095cf361bfea74d019039bc5a1495367b</sha1>
  </revision>
  <revision>
    <id>118</id>
    <parentid>117</parentid>
    <timestamp>2015-12-28T17:49:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2471" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Innovative Servicea 
&lt;/div&gt;
|}
|}

= Publications =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}

= Structuring =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Mission Assurance&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Operational Support&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}

= Documention Templates =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Support Capability =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>fb3e0589f1d0a979638500f40002d2b509c20781</sha1>
  </revision>
  <revision>
    <id>125</id>
    <parentid>118</parentid>
    <timestamp>2015-12-29T03:12:48Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2464" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Publications =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Reachback Capability&lt;/h2&gt;
|}

= Structuring =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Mission Assurance&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Operational Support&lt;/h2&gt;
|}
{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;Discrete Activites&lt;/h2&gt;
|}

= Documention Templates =

{| style="width:100%; vertical-align:top; background:#f5fffa;"
|-
| style="padding:2px" | &lt;h2 style="margin:3px; background:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;
|}

= Support Capability =
{| style="width:100%; vertical-align:top; backgrounf:#f5fffa;"
|-
|-
| style="padding:2px" | &lt;h2 style="margin:3px; backgroung:#eff4f2; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"&gt;
&lt;/h2&gt;

|}
= Knowledge Base  =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>e643e378c3a1733876aa7c2cff4f487a858695c0</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>Template:Item</title>
  <ns>10</ns>
  <id>57</id>
  <revision>
    <id>119</id>
    <timestamp>2015-12-29T01:04:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Item" template. It should be called in the following format: &lt;pre&gt; {{Item |Name= }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;includ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="251" xml:space="preserve">&lt;noinclude&gt;
This is the "Item" template.
It should be called in the following format:
&lt;pre&gt;
{{Item
|Name=
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
! Name
| [[Name::{{{Name|}}}]] 
|}
&lt;/includeonly&gt;</text>
    <sha1>17015c8d2583cbb496a466682e1e6c7b26a45b24</sha1>
  </revision>
  <revision>
    <id>120</id>
    <parentid>119</parentid>
    <timestamp>2015-12-29T01:04:27Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5535" xml:space="preserve">&lt;includeonly&gt;
=Citation=
{{#ask:[[{{FULLPAGENAME}}]]
|?Citation
|mainlabel=-
|headers=hide
|class=citationtable
}}
{| class="wikitable itemtable" style="width:100%;"
! Abstract
| {{#if:{{{abstract|}}}|{{{abstract}}}|&amp;nbsp;}}
|-
! Keywords
| {{#invoke:Utilities|parseMultiple|{{lc:{{{keywords|}}}}}|Keyword Link}}
|-
{{#if: {{{journal|}}}{{{year|}}}{{{publisher|}}}||&lt;div style="display:none"&gt;}}
{{Optional Table Row|Journal|{{{journal|}}}}}
{{Optional Table Row|Year|{{{year|}}}}}
{{Optional Table Row|Publisher|{{{publisher|}}}}}
|}
{{#if: {{{journal|}}}{{{year|}}}{{{publisher|}}}||&lt;/div&gt;}}
=Reviews=
&lt;div style="text-align:right;width:100%"&gt;
{{#if:{{CURRENTUSER}}|{{#formlink:form=Review|target=Review:{{PAGENAME}}/{{CURRENTUSER}}|link text={{#if:{{#ask:[[Review:{{PAGENAME}}/{{CURRENTUSER}}]]}}|Edit Your Review|Review This Item}}|link type=post button}}}}
&lt;/div&gt;
&lt;div style="display:none;"&gt;
{{#vardefine:fivestar|{{#show:{{FULLPAGENAME}}|?Five Star Review Count}}|0}}
{{#vardefine:fourstar|{{#show:{{FULLPAGENAME}}|?Four Star Review Count}}|0}}
{{#vardefine:threestar|{{#show:{{FULLPAGENAME}}|?Three Star Review Count}}|0}}
{{#vardefine:twostar|{{#show:{{FULLPAGENAME}}|?Two Star Review Count}}|0}}
{{#vardefine:onestar|{{#show:{{FULLPAGENAME}}|?One Star Review Count}}|0}}
{{#vardefine:max1|{{#ifexpr:{{#var:fivestar}}&gt;{{#var:fourstar}}|{{#var:fivestar}}|{{#var:fourstar}}}}}}
{{#vardefine:max2|{{#ifexpr:{{#var:threestar}}&gt;{{#var:twostar}}|{{#var:threestar}}|{{#var:twostar}}}}}}
{{#vardefine:max3|{{#ifexpr:{{#var:max1}}&gt;{{#var:max2}}|{{#var:max1}}|{{#var:max2}}}}}}
{{#vardefine:max4|{{#ifexpr:{{#var:onestar}}&gt;1|{{#var:onestar}}|1}}}}
{{#vardefine:max|{{#ifexpr:{{#var:max3}}&gt;{{#var:max4}}|{{#var:max3}}|{{#var:max4}}}}}}
&lt;/div&gt;{{Bar chart
| bar_width   = 15
| data_max    = {{#var:max}}
| label1   = {{Review Item Query|5 stars|5}}
| data1    = {{#var:fivestar}}
| label2   = {{Review Item Query|4 stars|4}}
| data2    = {{#var:fourstar}}
| label3   = {{Review Item Query|3 stars|3}}
| data3    = {{#var:threestar}}
| label4   = {{Review Item Query|2 stars|2}}
| data4    = {{#var:twostar}}
| label5   = {{Review Item Query|1 star|1}}
| data5    = {{#var:onestar}}
}}

{{#if:{{#urlget:rating}}|{{#vardefine:rating|[[Rating::{{#urlget:rating}}]]}}
{{Review Item Query|see all reviews}}

&lt;b&gt;{{#urlget:rating}} Star Reviews:&lt;/b&gt;
|{{#vardefine:rating| }}}}

{{#ask:[[Category:Reviews]][[Item::Item:{{PAGENAME}}]]{{#var:rating}}
|?Rating
|?Reviewer
|?Comments
|sort=Rating
|order=desc
|format=template
|template=Review Link Item
|default=no reviews
}}

&lt;div style="display:none;"&gt;
{{DEFAULTSORT:{{{title|}}}}}
{{#set:Full_Title={{{title|}}}}}
{{#set:Short_Title={{#sub:{{{title|}}}|0|40}}...}}
{{#set:Sorting Title={{lc:{{{title|}}}}}}}
{{#arraymap:{{{keywords|}}}|,|@@@@|{{#set:Keyword={{lc:@@@@}}}}}}
{{#set:Keyword Links={{#invoke:Utilities|parseMultiple|{{lc:{{{keywords|}}}}}|Keyword Link}}}}
{{#set:Year={{{year}}}}}
{{#set:Item Type={{{type}}}}}
{{#set:Journal={{{journal|}}}]]
{{#set:Publisher={{{publisher|}}}}}
{{#set:Abstract={{{abstract|}}}}}
{{#set:Average Rating Stars={{#invoke:Utilities|unstrip|{{#rating:{{#ask:[[Category:Reviews]][[Item::{{FULLPAGENAME}}]]|?Rating|format=average}}}}}}}}
{{#if: {{#ask:[[Category:Reviews]][[Item::{{FULLPAGENAME}}]]|?Rating}} |
{{#switch: {{#ask: [[Category:Reviews]][[Item::{{FULLPAGENAME}}]]|?Rating|format=average}}
| 1 = {{#set:Average Rating=&amp;#9734;}}{{#set:Average Rating Number=1}}
| 2 = {{#set:Average Rating=&amp;#9734; &amp;#9734;}} {{#set:Average Rating Number=2}}
| 3 = {{#set:Average Rating=&amp;#9734; &amp;#9734; &amp;#9734;}} {{#set:Average Rating Number=3}}
| 4 = {{#set:Average Rating=&amp;#9734; &amp;#9734; &amp;#9734; &amp;#9734;}} {{#set:Average Rating Number=4}}
| 5 = {{#set:Average Rating=&amp;#9734; &amp;#9734; &amp;#9734; &amp;#9734; &amp;#9734;}} {{#set:Average Rating Number=5}}
| default = {{#set:Average Rating=not rated}} {{#set:Average Rating Number=0}}
}} | {{#set:Average Rating=not rated}}{{#set:Average Rating Number=0}}}}
{{#ratingAfterTitle:{{#ask:[[Category:Reviews]][[Item::{{FULLPAGENAME}}]]|?Rating|format=average}}}}
{{#set:Five Star Review Count={{#ask:[[Category:Reviews]][[Item::{{FULLPAGENAME}}]][[Rating::5]]|format=count|default=0}}}}
{{#set:Four Star Review Count={{#ask:[[Category:Reviews]][[Item::{{FULLPAGENAME}}]][[Rating::4]]|format=count|default=0}}}}
{{#set:Three Star Review Count={{#ask:[[Category:Reviews]][[Item::{{FULLPAGENAME}}]][[Rating::3]]|format=count|default=0}}}}
{{#set:Two Star Review Count={{#ask:[[Category:Reviews]][[Item::{{FULLPAGENAME}}]][[Rating::2]]|format=count|default=0}}}}
{{#set:One Star Review Count={{#ask:[[Category:Reviews]][[Item::{{FULLPAGENAME}}]][[Rating::1]]|format=count|default=0}}}}
{{#set:Item Type Image=&lt;div style="text-align:center;"&gt;[[Image:{{{type}}}.png|link=|48px|{{{type}}}]]&lt;br /&gt;&lt;span style="font-size:xx-small;"&gt;{{{type}}}&lt;/span&gt;&lt;/div&gt;}}
{{#set:Citation=
'''[[{{FULLPAGENAME}}|{{{title|}}}]]''' by {{{authors|}}} {{#if: {{{year|}}} | {{{year|}}} | }}  | }} &lt;br/&gt;
}}
{{#set:Title Icon={{{type}}}.png}}

{{#set:Responsive Citation=&lt;div class="row"&gt;&lt;div class="large-1 column"&gt;[[Image:{{{type}}}.png|24px|link=]]&lt;/div&gt;&lt;div class="large-2 column"&gt;{{#invoke:Utilities|unstrip|{{#rating:{{#ask:[[Category:Reviews]][[Item::{{FULLPAGENAME}}]]|?Rating|format=average}}}}}}&lt;/div&gt;&lt;div class="large-9 columns"&gt;'''[[{{FULLPAGENAME}}|{{{title|}}}]]'''{{#if: {{{year|}}} | , {{{year|}}} | }}&lt;/div&gt;&lt;/div&gt;}}

[[Category:Items]]
&lt;headertabs&gt;&lt;headertabs/&gt;
&lt;/div&gt;
{{#var:stars}}
&lt;/includeonly&gt;&lt;noinclude&gt;[[Category:Framework Pages]]&lt;/noinclude&gt;</text>
    <sha1>4e25a7df5eae1cff1a1d9ba3833711b04fa55296</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>Form:Item</title>
  <ns>106</ns>
  <id>58</id>
  <revision>
    <id>121</id>
    <timestamp>2015-12-29T01:05:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Item" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit th..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="995" xml:space="preserve">&lt;noinclude&gt;
This is the "Item" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=Item}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Item}}}
{| class="formtable"
! Type: 
| {{{field|type}}}
|-
! Abstract: 
| {{{field|abstract}}}
|-
! Keywords: 
| {{{field|keywords}}}
|-
! Journal: 
| {{{field|journal}}}
|-
! Year: 
| {{{field|year}}}
|-
! Publisher: 
| {{{field|publisher}}}
|-
! Title: 
| {{{field|title}}}
|-
! Authors: 
| {{{field|authors}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>ac2f6106f79cbd7b986303a4022acd39545ef479</sha1>
  </revision>
  <revision>
    <id>122</id>
    <parentid>121</parentid>
    <timestamp>2015-12-29T01:06:41Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1485" xml:space="preserve">&lt;includeonly&gt;
{{{info|page name=Item:&lt;unique number;start=1&gt;|create title=Add Item}}}
{{{for template|Item}}}
{|class="formtable"  style="border: none;"
| {{{standard input|save|label=Save}}} {{{standard input|cancel}}}
|-
| style="vertical-align:top;" | '''Citation Title'''
| style="vertical-align:top;" | {{{field|title|input type=textarea|cols=80|rows=2|mandatory}}}
|-
| style="vertical-align:top;" |'''Year'''
| style="vertical-align:top;" | {{{field|year|input type=textarea|cols=5|rows|1|mandatory}}}
|-
| style="vertical-align:top;" | '''Journal'''
| {{{field|journal|input type=text|size=80}}}
|-
| style="vertical-align:top;" |'''Publisher'''
| {{{field|publisher|input type=textarea|rows=1|cols=50}}}
|-
| style="vertical-align:top;" | '''Authors (FN MI LN)''' 
| style="vertical-align:top;" | {{{field|authors|holds template}}}
|-
| style="vertical-align:top;" | '''Keywords'''
|  {{{field|keywords|input type=tokens}}}
|-
| style="vertical-align:top;" | '''Media Type'''
| {{{field|type|input type=listbox|default=article|mandatory|size=10}}}
|-
| style="vertical-align:top;" | '''Abstract'''
| {{{field|abstract|input type=textarea|editor=wikieditor}}} 
|-
| {{{standard input|save|label=Save}}} {{{standard input|cancel}}}
|}
{{{end template}}}
{{{for template|Author|embed in field=Item[authors]|multiple|add button text=Add an Author}}}
{{{field|author|input type=text|size=40}}}
{{{end template}}}
&lt;/includeonly&gt;
&lt;noinclude&gt;
[[Category:Framework Pages]]
&lt;/noinclude&gt;</text>
    <sha1>65826065ad5b4aea274e3338f34faea5bef474fd</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>Property:Item Type</title>
  <ns>102</ns>
  <id>59</id>
  <revision>
    <id>123</id>
    <timestamp>2015-12-29T01:14:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
  <revision>
    <id>124</id>
    <parentid>123</parentid>
    <timestamp>2015-12-29T01:14:27Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="492" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]

[[Allows value::article]]
[[Allows value::book]]
[[Allows value::booklet]]
[[Allows value::conference]]
[[Allows value::inbook]]
[[Allows value::incollection]]
[[Allows value::inproceedings]]
[[Allows value::manual]]
[[Allows value::mastersthesis]]
[[Allows value::misc]]
[[Allows value::phdthesis]]
[[Allows value::proceedings]]
[[Allows value::standard]]
[[Allows value::techreport]]
[[Allows value::unpublished]]</text>
    <sha1>abcd7257bbc4f8f15fdc7663c0b0f654f7b111a9</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>Cyber Early Warning</title>
  <ns>0</ns>
  <id>60</id>
  <revision>
    <id>126</id>
    <timestamp>2015-12-29T03:46:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "== Overview =="</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14" xml:space="preserve">== Overview ==</text>
    <sha1>d27702e19830e4761cc4d2ae69628ba03faca2d0</sha1>
  </revision>
  <revision>
    <id>127</id>
    <parentid>126</parentid>
    <timestamp>2015-12-29T11:31:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3910" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment in context of an evolved state maturity and an advanced Cyber capable operation summarized in describing the following:

== INDUSTRY STATE OF PRACTICE ==
 
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.</text>
    <sha1>514b05c392469d0e2c8ccd64b4cf32f027f81103</sha1>
  </revision>
  <revision>
    <id>129</id>
    <parentid>127</parentid>
    <timestamp>2015-12-29T11:37:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3839" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|thumbnail]]
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.</text>
    <sha1>3cafa3fc2bb7ff006e1d02e7ca508693fc922f54</sha1>
  </revision>
  <revision>
    <id>130</id>
    <parentid>129</parentid>
    <timestamp>2015-12-29T11:38:40Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3842" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|340px|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.</text>
    <sha1>244d5cc33af15d730d440c90b35ecfd60331c3a7</sha1>
  </revision>
  <revision>
    <id>131</id>
    <parentid>130</parentid>
    <timestamp>2015-12-29T11:39:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3836" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.</text>
    <sha1>14cb49ff1607ee8b1b39f297a1d5eaf3220b40d5</sha1>
  </revision>
  <revision>
    <id>135</id>
    <parentid>131</parentid>
    <timestamp>2015-12-29T11:45:27Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3869" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.

{{Cyber Early Warning Systems}}</text>
    <sha1>44a22543e2964f8ab2334ad15e426025fdab68ae</sha1>
  </revision>
  <revision>
    <id>136</id>
    <parentid>135</parentid>
    <timestamp>2015-12-29T11:46:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3861" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.

{{Cyber Early Warning}}</text>
    <sha1>7dd9915524621729b8093e4e9ee12414acf81c45</sha1>
  </revision>
  <revision>
    <id>139</id>
    <parentid>136</parentid>
    <timestamp>2015-12-29T11:50:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3863" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.

{{Early Warning Systems}}</text>
    <sha1>b2fe876f76aab63a5bf0d8f1f892baa5cfec08be</sha1>
  </revision>
  <revision>
    <id>142</id>
    <parentid>139</parentid>
    <timestamp>2015-12-29T11:54:43Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3879" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.

{{Early Warning Systems}}

{{TRADECRAFT}}</text>
    <sha1>41e0b65583272bc368b36ebe61d8e4140721306d</sha1>
  </revision>
  <revision>
    <id>143</id>
    <parentid>142</parentid>
    <timestamp>2015-12-29T11:56:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3884" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.

{{EARLY WARNING SYSTEMS}} 

{{THE TRADECRAFT}}</text>
    <sha1>a07bfcccde49670657b26a3a16c739012d9255ea</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>File:Warning-intelligence-image.png</title>
  <ns>6</ns>
  <id>61</id>
  <revision>
    <id>128</id>
    <timestamp>2015-12-29T11:35:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>Template:New Paragraph</title>
  <ns>10</ns>
  <id>62</id>
  <revision>
    <id>132</id>
    <timestamp>2015-12-29T11:41:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;includeonly&gt; &lt;div class="np"&gt;&lt;/div&gt; &lt;/includeonly&gt;&lt;noinclude&gt;[[Category:Framework Pages]]&lt;/noinclude&gt;"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="102" xml:space="preserve">&lt;includeonly&gt;
&lt;div class="np"&gt;&lt;/div&gt;
&lt;/includeonly&gt;&lt;noinclude&gt;[[Category:Framework Pages]]&lt;/noinclude&gt;</text>
    <sha1>4de0b1b5b72807dfd76e4dafde6bab88c4430c85</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>Template:Early Warning System Types</title>
  <ns>10</ns>
  <id>63</id>
  <revision>
    <id>133</id>
    <timestamp>2015-12-29T11:42:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Early Warning System Types" template. It should be called in the following format: &lt;pre&gt; {{Early Warning System Types }} &lt;/pre&gt; Edit the page to see t..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="256" xml:space="preserve">&lt;noinclude&gt;
This is the "Early Warning System Types" template.
It should be called in the following format:
&lt;pre&gt;
{{Early Warning System Types
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>7e5f15413a7cebf69688705ba3504e1ecbb440ef</sha1>
  </revision>
  <revision>
    <id>134</id>
    <parentid>133</parentid>
    <timestamp>2015-12-29T11:44:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1708" xml:space="preserve">== EARLY WARNING SYSTEMS ==

'''Crisis and catastrophic event based '''

Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based '''
Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.  


�</text>
    <sha1>51896e1e2fefa024a93261d92c68cd6d0756ef7a</sha1>
  </revision>
</page>
<page arvcontinue="20151227224502|94">
  <title>Template:Early Warning Systems</title>
  <ns>10</ns>
  <id>64</id>
  <revision>
    <id>137</id>
    <timestamp>2015-12-29T11:47:40Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "== EARLY WARNING SYSTEMS  ==  '''Crisis and catastrophic event based'''     Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1720" xml:space="preserve">== EARLY WARNING SYSTEMS  ==

'''Crisis and catastrophic event based'''  
 
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  
Activity and actor based
{{No Paragraph}}
Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.  


�</text>
    <sha1>856075414551b34604556d592f18f6f4b33ffd72</sha1>
  </revision>
  <revision>
    <id>138</id>
    <parentid>137</parentid>
    <timestamp>2015-12-29T11:48:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[Template:Cyber Early Warning]] to [[Template:Early Warning Systems]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1720" xml:space="preserve">== EARLY WARNING SYSTEMS  ==

'''Crisis and catastrophic event based'''  
 
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  
Activity and actor based
{{No Paragraph}}
Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.  


�</text>
    <sha1>856075414551b34604556d592f18f6f4b33ffd72</sha1>
  </revision>
  <revision>
    <id>140</id>
    <parentid>138</parentid>
    <timestamp>2015-12-29T11:52:41Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* EARLY WARNING SYSTEMS */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1720" xml:space="preserve">== EARLY WARNING SYSTEMS  ==

'''Crisis and catastrophic event based'''  
 
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically 
local alerts of potential crisis or issues of safety to the public..  
{{No Paragraph}}
'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.</text>
    <sha1>76f9ecc01e29144cced1b3664aa4f34a6fb0041e</sha1>
  </revision>
  <revision>
    <id>141</id>
    <parentid>140</parentid>
    <timestamp>2015-12-29T11:53:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* EARLY WARNING SYSTEMS */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1722" xml:space="preserve">== EARLY WARNING SYSTEMS  ==

'''Crisis and catastrophic event based'''  
 
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically 
local alerts of potential crisis or issues of safety to the public..  
{{New Paragraph}}

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.</text>
    <sha1>b8c6bf951ccfecd23a57e361853a0ce0629178c7</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>Cyber Early Warning</title>
  <ns>0</ns>
  <id>60</id>
  <revision>
    <id>144</id>
    <parentid>143</parentid>
    <timestamp>2015-12-29T11:57:52Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3888" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.

{{Early Warning System Types}}

{{THE TRADECRAFT}}</text>
    <sha1>bf9d251a5ba12fa394aef871862d74613c76be2b</sha1>
  </revision>
  <revision>
    <id>148</id>
    <parentid>144</parentid>
    <timestamp>2015-12-29T12:04:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3921" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.

{{Early Warning Systems|EARLY WARNING SYSTEMS}}}

{{THE TRADECRAFT|THE TRADECRAFT}}</text>
    <sha1>a033970a7eba2239c444ea64e1f4947fecc92256</sha1>
  </revision>
  <revision>
    <id>149</id>
    <parentid>148</parentid>
    <timestamp>2015-12-29T12:05:46Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3934" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.

== {{Early Warning Systems|EARLY WARNING SYSTEMS}}} ==

== {{THE TRADECRAFT|THE TRADECRAFT}}
 ==</text>
    <sha1>5496331727db4c98ec8620fa150aa056cfe1c62b</sha1>
  </revision>
  <revision>
    <id>150</id>
    <parentid>149</parentid>
    <timestamp>2015-12-29T12:06:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3927" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.

== {{Early Warning Systems|EARLY WARNING SYSTEMS}}} ==

{{THE TRADECRAFT|THE TRADECRAFT}}</text>
    <sha1>de7290618166bca37cd0c4bc9d8df58dc86b092f</sha1>
  </revision>
  <revision>
    <id>151</id>
    <parentid>150</parentid>
    <timestamp>2015-12-29T12:07:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3933" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.

== {{Early Warning Systems|EARLY WARNING SYSTEMS}}} ==

== {{THE TRADECRAFT|THE TRADECRAFT}} ==</text>
    <sha1>c4a2939d9ad721c2e7bfda3fc704a5534adfd316</sha1>
  </revision>
  <revision>
    <id>152</id>
    <parentid>151</parentid>
    <timestamp>2015-12-29T12:09:42Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4197" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== KEY ELEMENTS ==
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
== {{Early Warning Systems|EARLY WARNING SYSTEMS}}} ==

== {{THE TRADECRAFT|THE TRADECRAFT}} ==</text>
    <sha1>10501970ea021c679d48cfa407c96fd56385cf02</sha1>
  </revision>
  <revision>
    <id>153</id>
    <parentid>152</parentid>
    <timestamp>2015-12-29T12:10:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4204" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== KEY ELEMENTS ==
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}

{{Early Warning Systems|EARLY WARNING SYSTEMS}}}
{{New Paragraph}}

{{THE TRADECRAFT|THE TRADECRAFT}}</text>
    <sha1>b74369af2ee8ebe69ed5b98e8e896cc5a36e99d9</sha1>
  </revision>
  <revision>
    <id>154</id>
    <parentid>153</parentid>
    <timestamp>2015-12-29T12:11:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4167" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== KEY ELEMENTS ==
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}

{{Early Warning Systems}}}
{{New Paragraph}}

{{THE TRADECRAFT}}</text>
    <sha1>bf34e47181d1fd8759f12dcd84767e4dfc597e88</sha1>
  </revision>
  <revision>
    <id>155</id>
    <parentid>154</parentid>
    <timestamp>2015-12-29T12:12:40Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4174" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== KEY ELEMENTS ==
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}

=={{Early Warning Systems}} ==
{{New Paragraph}} ==

{{THE TRADECRAFT}}</text>
    <sha1>acb3c44d3046d6532957734804b194166d921b34</sha1>
  </revision>
  <revision>
    <id>156</id>
    <parentid>155</parentid>
    <timestamp>2015-12-29T12:14:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* {{Early Warning Systems}} */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4169" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== KEY ELEMENTS ==
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}

{{Early Warning Systems}}
{{New Paragraph}} ==

{{THE TRADECRAFT}}</text>
    <sha1>21151193a44a8c41412ebf81c86b463f83f81f01</sha1>
  </revision>
  <revision>
    <id>157</id>
    <parentid>156</parentid>
    <timestamp>2015-12-29T12:14:47Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4166" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== KEY ELEMENTS ==
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}

{{Early Warning Systems}}
{{New Paragraph}}

{{THE TRADECRAFT}}</text>
    <sha1>573486d4a3740bd69283ea162a98e575ea59f12a</sha1>
  </revision>
  <revision>
    <id>158</id>
    <parentid>157</parentid>
    <timestamp>2015-12-29T12:18:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5824" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== KEY ELEMENTS ==
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}

== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.</text>
    <sha1>2b684546789b68431262556374e04ac1d6cc4a8c</sha1>
  </revision>
  <revision>
    <id>159</id>
    <parentid>158</parentid>
    <timestamp>2015-12-29T12:23:52Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7915" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.

== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}

KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.</text>
    <sha1>dd23854ceecbe1fa900866fa5b7e86838632bf3c</sha1>
  </revision>
  <revision>
    <id>160</id>
    <parentid>159</parentid>
    <timestamp>2015-12-29T12:24:56Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7913" xml:space="preserve">==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.</text>
    <sha1>a0baaba08daa4bcbef845d39f7d9d8e5d3b490a0</sha1>
  </revision>
  <revision>
    <id>161</id>
    <parentid>160</parentid>
    <timestamp>2015-12-29T12:25:28Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7931" xml:space="preserve">__NOEDITSECTION__
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|link=]]

As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.</text>
    <sha1>d0f94a532e1c63aa11856fba9e01f962e323045e</sha1>
  </revision>
  <revision>
    <id>162</id>
    <parentid>161</parentid>
    <timestamp>2015-12-29T12:26:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7945" xml:space="preserve">__NOEDITSECTION__
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
[[File:Warning-intelligence-image.png|Thumbnail|rightlink=]]
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.</text>
    <sha1>b1495d3dfa648602170bf971dffccade37bfc3b2</sha1>
  </revision>
  <revision>
    <id>163</id>
    <parentid>162</parentid>
    <timestamp>2015-12-29T12:27:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7945" xml:space="preserve">__NOEDITSECTION__
==SUMMARY ==
[[File:Warning-intelligence-image.png|Thumbnail|rightlink=]]
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.</text>
    <sha1>356c08d224339577c7f437404bf6d91d7276028b</sha1>
  </revision>
  <revision>
    <id>164</id>
    <parentid>163</parentid>
    <timestamp>2015-12-29T12:28:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7935" xml:space="preserve">__NOEDITSECTION__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.</text>
    <sha1>aef6ac87c85b5b7d6890ac71eca11a9ba55f4655</sha1>
  </revision>
  <revision>
    <id>165</id>
    <parentid>164</parentid>
    <timestamp>2015-12-29T12:28:49Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7945" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.</text>
    <sha1>8822fabc4a54da6763bdf756c184cdcf9c5ef6d8</sha1>
  </revision>
  <revision>
    <id>166</id>
    <parentid>165</parentid>
    <timestamp>2015-12-29T12:31:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8091" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon={{PAGENAME}}}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]
[[Compatible with::NATO]]</text>
    <sha1>710781851af1a72b7fb7199f589812548d83bc1f</sha1>
  </revision>
  <revision>
    <id>167</id>
    <parentid>166</parentid>
    <timestamp>2015-12-29T12:32:01Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8087" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon={{PAGENAME}}}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]
[[Aligns with::NATO]]</text>
    <sha1>360ac192e058b1c99f949e8487c6a6a94b1f8470</sha1>
  </revision>
  <revision>
    <id>168</id>
    <parentid>167</parentid>
    <timestamp>2015-12-29T12:34:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8092" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-warning.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]
[[Aligns with::NATO]]</text>
    <sha1>f614bb606332b335171b8491b730c258e59ca6aa</sha1>
  </revision>
  <revision>
    <id>169</id>
    <parentid>168</parentid>
    <timestamp>2015-12-29T12:37:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8092" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-Warning.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]
[[Aligns with::NATO]]</text>
    <sha1>7e2f0504f5f73b6f39b6ca528befe2c63958b5fb</sha1>
  </revision>
  <revision>
    <id>170</id>
    <parentid>169</parentid>
    <timestamp>2015-12-29T12:39:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8098" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragra}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-Warning-image.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]
[[Aligns with::NATO]]</text>
    <sha1>3664de1d6d46263225e2f885547281f79d905baa</sha1>
  </revision>
  <revision>
    <id>174</id>
    <parentid>170</parentid>
    <timestamp>2015-12-29T12:43:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8100" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragraph}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-Warning-image.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]
[[Aligns with::NATO]]</text>
    <sha1>2dff9e9504fc0e3c7db64b7fc1d92a644c3938af</sha1>
  </revision>
  <revision>
    <id>176</id>
    <parentid>174</parentid>
    <timestamp>2015-12-29T12:45:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8102" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragraph}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-Warning-image.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]
[[Aligns with::NATO| ]]</text>
    <sha1>3ba1dae9a8043156bb4334d8a9d928b746eab28f</sha1>
  </revision>
  <revision>
    <id>177</id>
    <parentid>176</parentid>
    <timestamp>2015-12-29T12:53:17Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9598" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragraph}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.
== Structure ==
STRUCTURE
An emphasis on cyber resilience and decreasing the emphasis on cyber defense will focus on the effects against an adversarial attempts in attacking.  Below are some examples of tactic characteristics and the effects they may have.  This differs greatly from the typical approaches in cyber defense and attempting to stop an attacker through network and system controls. 
{{New Paragraph}} 
It is safe to assume an increasing rapid exposure by the private sector to military and government will result in a drastic changing of networks and systems.  Most corporate professionals lack exposure in the cyber maneuvering or experience in security in depth and breadth including network address changing rapidly proven to hinder attackers from the inability in the existing tools.  When considering an infrastructure modernization, expect to see an increasing movement towards rapid dynamic networks from the changing addresses and nodes within dynamically created, joining, splitting and removing that allows better allocation of resources but more important poses an extremely increased level of difficulty from an attacker’s view.  Regardless if these are ever implemented with the organization below are examples of characterizing the effects to an adversaries that will help provide the organization an unmatched capability in the threat operations area and the capability componentization for guiding future capability introduction.    

[[File:Effects.png|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-Warning-image.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]
[[Aligns with::NATO| ]]</text>
    <sha1>16b08d80136773a380389bd8b9dea40e2c48235f</sha1>
  </revision>
  <revision>
    <id>179</id>
    <parentid>177</parentid>
    <timestamp>2015-12-29T12:57:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9590" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragraph}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

== Structure ==

An emphasis on cyber resilience and decreasing the emphasis on cyber defense will focus on the effects against an adversarial attempts in attacking.  Below are some examples of tactic characteristics and the effects they may have.  This differs greatly from the typical approaches in cyber defense and attempting to stop an attacker through network and system controls. 
{{New Paragraph}} 
It is safe to assume an increasing rapid exposure by the private sector to military and government will result in a drastic changing of networks and systems.  Most corporate professionals lack exposure in the cyber maneuvering or experience in security in depth and breadth including network address changing rapidly proven to hinder attackers from the inability in the existing tools.  When considering an infrastructure modernization, expect to see an increasing movement towards rapid dynamic networks from the changing addresses and nodes within dynamically created, joining, splitting and removing that allows better allocation of resources but more important poses an extremely increased level of difficulty from an attacker’s view.  Regardless if these are ever implemented with the organization below are examples of characterizing the effects to an adversaries that will help provide the organization an unmatched capability in the threat operations area and the capability componentization for guiding future capability introduction.    

[[File:Effects.png|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-Warning-image.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]
[[Aligns with::NATO| ]]</text>
    <sha1>653e51946183c7f5514167651f68b11798697c78</sha1>
  </revision>
  <revision>
    <id>180</id>
    <parentid>179</parentid>
    <timestamp>2015-12-29T12:58:42Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9566" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragraph}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

== Structure ==

An emphasis on cyber resilience and decreasing the emphasis on cyber defense will focus on the effects against an adversarial attempts in attacking.  Below are some examples of tactic characteristics and the effects they may have.  This differs greatly from the typical approaches in cyber defense and attempting to stop an attacker through network and system controls. 
{{New Paragraph}} 
It is safe to assume an increasing rapid exposure by the private sector to military and government will result in a drastic changing of networks and systems.  Most corporate professionals lack exposure in the cyber maneuvering or experience in security in depth and breadth including network address changing rapidly proven to hinder attackers from the inability in the existing tools.  When considering an infrastructure modernization, expect to see an increasing movement towards rapid dynamic networks from the changing addresses and nodes within dynamically created, joining, splitting and removing that allows better allocation of resources but more important poses an extremely increased level of difficulty from an attacker’s view.  Regardless if these are ever implemented with the organization below are examples of characterizing the effects to an adversaries that will help provide the organization an unmatched capability in the threat operations area and the capability componentization for guiding future capability introduction.    

[[File:Effects.png|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-Warning-image.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]</text>
    <sha1>cb43caf719d8239d780955544e02c387a97c9f9c</sha1>
  </revision>
  <revision>
    <id>182</id>
    <parentid>180</parentid>
    <timestamp>2015-12-29T13:05:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9571" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragraph}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.
== THE TRADECRAFT ==
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

== Structure ==

An emphasis on cyber resilience and decreasing the emphasis on cyber defense will focus on the effects against an adversarial attempts in attacking.  Below are some examples of tactic characteristics and the effects they may have.  This differs greatly from the typical approaches in cyber defense and attempting to stop an attacker through network and system controls. 
{{New Paragraph}} 
It is safe to assume an increasing rapid exposure by the private sector to military and government will result in a drastic changing of networks and systems.  Most corporate professionals lack exposure in the cyber maneuvering or experience in security in depth and breadth including network address changing rapidly proven to hinder attackers from the inability in the existing tools.  When considering an infrastructure modernization, expect to see an increasing movement towards rapid dynamic networks from the changing addresses and nodes within dynamically created, joining, splitting and removing that allows better allocation of resources but more important poses an extremely increased level of difficulty from an attacker’s view.  Regardless if these are ever implemented with the organization below are examples of characterizing the effects to an adversaries that will help provide the organization an unmatched capability in the threat operations area and the capability componentization for guiding future capability introduction.    

[[File:Effects-advr.png|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-Warning-image.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]</text>
    <sha1>da471593567934723d3c16482ee0f6a76563482b</sha1>
  </revision>
  <revision>
    <id>184</id>
    <parentid>182</parentid>
    <timestamp>2015-12-29T13:09:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9566" xml:space="preserve">__NOEDITSECTION__
__NOTOC__
[[File:Warning-intelligence-image.png|rightlink=]]
==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragraph}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.

= TRADECRAFT =
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

== Structure ==

An emphasis on cyber resilience and decreasing the emphasis on cyber defense will focus on the effects against an adversarial attempts in attacking.  Below are some examples of tactic characteristics and the effects they may have.  This differs greatly from the typical approaches in cyber defense and attempting to stop an attacker through network and system controls. 
{{New Paragraph}} 
It is safe to assume an increasing rapid exposure by the private sector to military and government will result in a drastic changing of networks and systems.  Most corporate professionals lack exposure in the cyber maneuvering or experience in security in depth and breadth including network address changing rapidly proven to hinder attackers from the inability in the existing tools.  When considering an infrastructure modernization, expect to see an increasing movement towards rapid dynamic networks from the changing addresses and nodes within dynamically created, joining, splitting and removing that allows better allocation of resources but more important poses an extremely increased level of difficulty from an attacker’s view.  Regardless if these are ever implemented with the organization below are examples of characterizing the effects to an adversaries that will help provide the organization an unmatched capability in the threat operations area and the capability componentization for guiding future capability introduction.    

[[File:Effects-advr.png|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-Warning-image.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]</text>
    <sha1>e79c6e963b5f3f416a334b59efd3aba5ae10e263</sha1>
  </revision>
  <revision>
    <id>185</id>
    <parentid>184</parentid>
    <timestamp>2015-12-29T13:10:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9557" xml:space="preserve">[[File:Warning-intelligence-image.png|rightlink=]]
__NOEDITSECTION__

==SUMMARY ==
Distinguishing the differences between Early Warning Systems (EWS) can be broadly described by those intended focus of Warning in order to Alert to prepare, the other focus of Alert in order to Warn to prevent.  This difference provides very different characteristics fundamental in the approaches and engineering required with an understanding in both.  The following descriptions attempt to further illustrate differences between the effects resulting from an event and effects from an action in their objectives.

== PURPOSE ==
To further help communication this purpose the most effective method is illustrating within the conceptual model of the organization’s environment.

== INDUSTRY STATE OF PRACTICE ==
As part of the overall enterprise strategy the organization’s implementation of a comprehensive “Cyber” program provide the foundation and program pillars.  To achieve this requires addressing some of the most complex issues organizations are facing.  Many of which lack the understanding that their capabilities over the next several years built on the foundations being put in place today.  
{{New Paragraph}}
An example is the information security industry’s “threat intelligence” and movement to an intelligence lead approach to security.  There are fundamental problems with this organizations must consider.  While the idea and concept of this is certainly a major step in the right direction, an intelligence lead approach to security being lead by professionals in the intelligence field is an absolute necessity (the security industry taking the intelligence lead is an approach critically crippled)  

== UNDERSTANDING EARLY WARNING ==
One of the most well known examples of early warning is the Distant Early Warning (DEW) Line set up by the United States and Canada during the early days of the Cold War.  But detecting an inbound attack is only a small part of early warning, a fact much overlooked in the cyber field, rooted in a mistaken belief that cyber incidents happen so quickly that “early” has to be measured in milliseconds.  Accordingly, much of what passes for cyber early warning is actually tactical warning and attack assessment (TW/AA) to detect attacks immediately and determine how serious they may be. 
{{New Paragraph}}
However, any warnings provided through TW/AA—whether for nuclear forces or cyber attacks—are not very early, providing only hours to minutes for decision makers to react. Since the real goal for early warning is to detect attacks in time to put sufficient countermeasures in place beforehand to stop the attack or minimize its effects, the short timelines of TW/AA generally are not enough on its own. 
Accordingly, providing earlier, strategic warning of attacks —weeks or even months ahead, an intelligence task, a key element of which determine if the geopolitical or socio-cultural situation becoming so tense an adversary would be willing to launch an attack.
Cyber warning is no different: to have the maximum time to respond, defenders must not only be able to detect inbound attacks but also look for the intent of adversaries before they actually decide to turn the launch key (or press the enter key).
{{New Paragraph}}
Unfortunately, because of the technical nature of the domain and its practitioners, “early warning for cyber attacks” often is equated to only computer networking products monitoring for hostile zeroes and ones inbound on the wire. This kind of cyber warning is plagued by multiple problems, each difficult and together sometimes insurmountable, such as issues detecting malicious attacks in massive flows of Internet traffic and determining if different attacks are part of the same campaign, especially when multiple organizations have been targeted.
{{New Paragraph}}
== EARLY WARNING SYSTEMS == 

'''Crisis and catastrophic event based'''
   
Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
{{New Paragraph}}
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based'''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.

= TRADECRAFT =
'''Strategic Cyber Early Warning - An Adaptive Approach''' 

* '''KEY ELEMENTS''' 
 Risk Knowledge 
 Monitoring and Warning Services
 Dissemination and Communication
 Threat Operation (analysis and countermeasures)
 Contingency (crisis management)
 Response (rapid response of incident event)  
{{New Paragraph}}
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts. 
{{New Paragraph}}
Accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.

== Structure ==

An emphasis on cyber resilience and decreasing the emphasis on cyber defense will focus on the effects against an adversarial attempts in attacking.  Below are some examples of tactic characteristics and the effects they may have.  This differs greatly from the typical approaches in cyber defense and attempting to stop an attacker through network and system controls. 
{{New Paragraph}} 
It is safe to assume an increasing rapid exposure by the private sector to military and government will result in a drastic changing of networks and systems.  Most corporate professionals lack exposure in the cyber maneuvering or experience in security in depth and breadth including network address changing rapidly proven to hinder attackers from the inability in the existing tools.  When considering an infrastructure modernization, expect to see an increasing movement towards rapid dynamic networks from the changing addresses and nodes within dynamically created, joining, splitting and removing that allows better allocation of resources but more important poses an extremely increased level of difficulty from an attacker’s view.  Regardless if these are ever implemented with the organization below are examples of characterizing the effects to an adversaries that will help provide the organization an unmatched capability in the threat operations area and the capability componentization for guiding future capability introduction.    

[[File:Effects-advr.png|link= ]]


{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Early-Warning-image.jpg}}
{{DISPLAYTITLE: Reachback Cell}}
[[Developed by::OSEC| ]]</text>
    <sha1>0bf402a37d6608dc930842c1f11669a13d8def1a</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>Template:THE TRADECRAFT</title>
  <ns>10</ns>
  <id>65</id>
  <revision>
    <id>145</id>
    <timestamp>2015-12-29T11:59:48Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "THE TRADECRAFT Indicator Lists: Compiling Indications... Fundamentals of Indications Analysis….. Specifics of the Analytical Method . . . . . Strategic Cyber Early Warning -..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2205" xml:space="preserve">THE TRADECRAFT
Indicator Lists: Compiling Indications...
Fundamentals of Indications Analysis…..
Specifics of the Analytical Method . . . . .
Strategic Cyber Early Warning - An Adaptive Approach 
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   
{{New Pargraph}}
Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers. 
�</text>
    <sha1>81108482b5447d1a71c36756c4d45af3fbb7d0c7</sha1>
  </revision>
  <revision>
    <id>146</id>
    <parentid>145</parentid>
    <timestamp>2015-12-29T12:00:49Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2201" xml:space="preserve">THE TRADECRAFT
Indicator Lists: Compiling Indications...
Fundamentals of Indications Analysis…..
Specifics of the Analytical Method . . . . .
Strategic Cyber Early Warning - An Adaptive Approach 
KEWAS design is to be a much more inclusive warning system than current ‘out of the box’ solutions and to take account of the risks identified through an intelligence assessment and Center of Gravity methodology. To accomplish this task, the KEWAS is based on the informed judgment of analysts accordingly and in contrast to offerings by industry, the KEWAS relies on qualitative analytical processes, not the more mechanical measurement of multiple, precisely defined and specific events. As such, it covers not only threats to the organization’s computer networks, but also a wide variety of technical and non-technical risk indicators, including uncertainty and instability in and around the Area of Responsibility.   
{{New Paragraph}}
Moreover, it both provides warning of any developing instability, crisis, threats, risks, or concerns that could impact on the security interests of the organization and it monitors deescalation of a crisis. 
After a Warning Problem is established, the KEWAS will monitor it on a monthly basis, or more if required. It is important to understand that "warning" is not an event, but a cyclical process in which an identifiable crisis or threat is assessed, a problem is defined and a critical indicator list is developed. 
{{New Paragraph}}
KEWAS will not only assess an identifiable crisis or threat but will identify an issue of concern as early as possible, establish a critical indicator list which provides indicators of how and how fast this issue is developing, and provide warning as appropriate. Clearly, this difficult in today's more complex and varied security environment. 
Next, the critical indicators are continuously monitored and the assessment matrix is updated as required. Warning is issued, and the cycle resumes. The crucial subtext to this process is recognition that the effectiveness of the warning is dependent upon the extent to which it is integrated into the crisis-management and response measures available to decision-makers.</text>
    <sha1>93b200b3acbee0fdb44cb6da14c4998260ce0a31</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>Template:Early Warning System Types</title>
  <ns>10</ns>
  <id>63</id>
  <revision>
    <id>147</id>
    <parentid>134</parentid>
    <timestamp>2015-12-29T12:01:52Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* EARLY WARNING SYSTEMS */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1709" xml:space="preserve">== EARLY WARNING SYSTEMS ==

'''Crisis and catastrophic event based '''

Alert to prepare an effect resulting from disaster or crisis event - for  purpose of this document the Alert focus EWS used to prepare are more commonly associated and familiar to the public.  Common examples are those intended for alerting the public of an event measured by some type catastrophic effect from Warning data, most commonly for disaster or crisis. Severe weather, or indicators Warning of potential crisis are generally based on geographical, or socio-cultural aspects related to geopolitical issues within an area capable of describing which may or may not be geographically isolated
Examples:  Local, regional and national emergency severe weather emergency alerts, FEMA model crisis and response alerts, geographically local alerts of potential crisis or issues of safety to the public..  

'''Activity and actor based '''

Warning to prevent, degrade, or disrupt effect of attack or activity action - much less commonly known to the public Early Warning Alert System used for an action based objective are highly evolved critical EWS immediately recognized requiring the importance across all services, followed by efforts eventually including military allies.  Joint Early Warning Systems include an Airborne Early Warning and Control System (AWACS) is based on air operations and sensors monitoring for Warning indications.  This is combined with an Intelligence Early Warning System enabled through working as a unified “Watch”.  Together they provide what is arguably the most advanced in the capabilities possible due to the nature in member nations operating in unity of effort and unity to achieve.  


�</text>
    <sha1>e86ad4d8a7e9f42f72edcc74e2feb7842a536cd2</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>File:Early-Warning.jpg</title>
  <ns>6</ns>
  <id>66</id>
  <revision>
    <id>171</id>
    <timestamp>2015-12-29T12:41:15Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>File:Early-Warning-image.jpg</title>
  <ns>6</ns>
  <id>67</id>
  <revision>
    <id>172</id>
    <timestamp>2015-12-29T12:41:33Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>173</id>
    <parentid>172</parentid>
    <timestamp>2015-12-29T12:41:40Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie uploaded a new version of [[File:Early-Morning-image.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>175</id>
    <parentid>173</parentid>
    <timestamp>2015-12-29T12:43:46Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[File:Early-Morning-image.jpg]] to [[File:Early-Warning-image.jpg]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>File:Effects.png</title>
  <ns>6</ns>
  <id>68</id>
  <revision>
    <id>178</id>
    <timestamp>2015-12-29T12:56:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>File:Effects-advr.png</title>
  <ns>6</ns>
  <id>69</id>
  <revision>
    <id>181</id>
    <timestamp>2015-12-29T13:04:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>Reachback Operations</title>
  <ns>0</ns>
  <id>43</id>
  <revision>
    <id>183</id>
    <parentid>125</parentid>
    <timestamp>2015-12-29T13:06:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="693" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]


{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}


&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>20f23558302c822ee2a8e0efc5b1fdf0ee54a32d</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>MediaWiki:Sidebar</title>
  <ns>8</ns>
  <id>41</id>
  <revision>
    <id>186</id>
    <parentid>51</parentid>
    <timestamp>2015-12-31T18:17:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">
* navigation
** mainpage|mainpage-description
* SEARCH
* TOOLBOX
* LANGUAGES</text>
    <sha1>43b17573551f2b5f534c1d71fb36fa72b645c402</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>MediaWiki:Common.css</title>
  <ns>8</ns>
  <id>40</id>
  <revision>
    <id>187</id>
    <parentid>50</parentid>
    <timestamp>2015-12-31T18:40:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>css</model>
    <format>text/css</format>
    <text bytes="5593" xml:space="preserve">/* CSS placed here will be applied to all skins */

/* MediaWiki overrides */
/* body.page-Main_Page h1.firstHeading { display:none; } */
#footer-info { display: none; } /* Hide footer */
li#ca-talk { display: none; } /* Hide discussion tab */
#pt-login { display: none; } /* Hide login text */
#p-tb { display: none; } /* Hide toolbox */
/* #ca-history { display: none; } /* Hide "View history" */


/* Elements */
code { background: none; font: 10pt courier,serif; }
h2 { margin-top: 15px; }
h3 { color: #222; font-size: 11pt; margin: 10px 0 -5px; }
ol img { display: block; margin: 10px 10px 20px; }
ol li {  }
p  { margin-top: 10px; }
pre { background: #efefef; border: none; font: 10pt courier,serif; margin: 15px 0; padding: 10px; }
tt { font-size: 10pt; }

/* Controls */
.searchButton { background: #eee; border: 1px solid #ccc; color: #333; font: bold 8pt sans-serif; height: 20px; }

/* Boxes */
.fullbox { border: 1px solid #ccc; margin:5px; }
.title { background: #e8f2f8; border: none; border-bottom: 1px solid #ccc; color: #0e3793; font: bold 14pt sans-serif; margin: 0; padding: 5px; }
.subtitle { font: bold 10pt sans-serif; }
.example { background: #efefef; display: block; margin: 15px 0; padding: 10px; }

/* Formatting */
.clear { clear: both; }
.code { font: 10pt courier,serif; }
.hash { color: #090; }
.content { padding: 10px; }

/* Special elements */
div#kx-linkbar img { margin-right: 20px; }


.row {min-width:90% !important;}
.toctoggle {display:none}

table.wikitable &gt; tr &gt; th, 
table.wikitable &gt; tr &gt;td, 
table.wikitable &gt; * &gt; tr &gt;th, 
table.wikitable &gt; * &gt; tr &gt; td {
padding: 1px;
}
/*
div#viki_0{
width:100% !important;
}*/
.vikijs-detail-panel {
border:none !important;
background:white !important;
font-size:90%;
}
.vikijs-graph-container {
border:none !important;
}
.smwtable .row-even {
	background-color:#FFF;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
.smwtable .row-odd .stripe {
	background-color:#f0f7f8;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
h3#tagline {display:none; }
#footer-privacy {display:none}
#footer-disclaimer {display:none}
#footer-about {display:none}
#footer-lastmod {font-size:70%;}
#footer-viewcount {font-size:70%;}

p.title {
color:#009933;
font-size:100%;
}
h2 {
 font-size:125%;
}

h5 {
color: #666666;
}
.mw-search-formheader  {display:none; }
.thumbinner {
padding-left:5px;
padding-top:5px;
padding-bottom:5px;
}
.thumbcaption {
font-size:100%;
color:#009933;
background: white;
text-align: center;
}

h4 {
color:#009933;
}

form#sfForm.createbox, .formtable, table.formtable tr {
 background-color:#F0F8FF  !important;
}
form#sfForm.createbox, table.formtable tbody tr td table {
border: 1px solid #F0F8FF  !important;
}
option {
    font-weight:normal;
   font-size: x-small;
}
.createboxInput {
       background-color:#FFFFFF  !important;
}
.navbar-item {
	color: white !important;
	font-weight: bold;
	padding-top: 9px;
	padding-right: 10px;
}
.title {
	color:#009933;
        text-align: left;
        font-size:150%;
}

.top-bar,
.top-bar-section ul,
.top-bar-section ul li.active &gt; a,
.top-bar-section li a:not(.button),
.top-bar-section .has-form {
background:#061734;
font-size:90%;
color: #FFFFFF;
}

.top-bar-section &gt; ul &gt; .divider,
.top-bar-section &gt; ul &gt; [role="separator"] {
  border-color: #164eaf;
}

/* Darker color for the hover over items */
.top-bar-section ul li.hover &gt; a,
.top-bar-section ul li ul.dropdown li.hover &gt; a{
    background: #113e8c;
}

/* Slightly darker color for the dropdowns*/ 
.top-bar-section ul li ul.dropdown li &gt; a {
    background: #061734;
}
.spacer {
        height: 30px;
}
.np {
        height: 15px;
}
.hierarchyText {
        font-size:80%;
        font-weight:bold;
        height: 20px;
}
.hierarchyText table tbody tr  {
       background-color: #d5f99b;
       border: 1px solid #BFE08B;
       height: 20px;
}

.examplebread table tbody tr {
 background-color: #ADDFFF;
}

.citationtable {
	border: solid 1px #BBBBBB;
}

.citationtable td {
	padding-left: 5px;
	padding-right: 5px;
	max-width: 600px;
}
.citationtablelong td {
	padding-left: 5px;
	padding-right: 5px;
}

.itemtable td {
	vertical-align: top;
	min-width: 200px;
}

.ratingselected a {
	font-weight: bold;
	color: orange !important;
}

.nowrap {
	white-space: nowrap;
}
.filtered-filters { 
    float: left;
    width: 30%;
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    background: transparent;
}

.filtered-filters .filtered-value .filtered-value-option {
    display: block !important;
    width: 90% !important;
    padding: 0 !important;
}
 
.filtered-views { 
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    max-height: 800px;
}
 
.filtered-views .filtered-list { 
    width: 95% !important;
}
 
.filter_name {
    width: 150px;
    background:#96aab2;
    color:black;
    text-align:left;
    align:left;
    border:1px solid #ddd;
    padding: 3px;
}
 
.filter_value {
    width: 400px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.filter_icon {
    width: 50px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.top-bar.expanded .title-area {
   background:#164eaf;
}

/* CSS placed here will be applied to all skins */
#ca-protect { display: none !important; } 
#ca-delete { display: none !important; } 
#ca-edit { display: none !important; } 
.toc, #toc { display: none; }</text>
    <sha1>0f516229cf1ea93817313721c7dc29e38934889c</sha1>
  </revision>
  <revision>
    <id>188</id>
    <parentid>187</parentid>
    <timestamp>2015-12-31T18:45:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>css</model>
    <format>text/css</format>
    <text bytes="5703" xml:space="preserve">/* CSS placed here will be applied to all skins */

.smwbuiltin a,
.smwbuiltin a.new {
    color: #FF8000;
}

/* CSS placed here will be applied to all skins */

/* MediaWiki overrides */
/* body.page-Main_Page h1.firstHeading { display:none; } */
#footer-info { display: none; } /* Hide footer */
li#ca-talk { display: none; } /* Hide discussion tab */
#pt-login { display: none; } /* Hide login text */
#p-tb { display: none; } /* Hide toolbox */
/* #ca-history { display: none; } /* Hide "View history" */


/* Elements */
code { background: none; font: 10pt courier,serif; }
h2 { margin-top: 15px; }
h3 { color: #222; font-size: 11pt; margin: 10px 0 -5px; }
ol img { display: block; margin: 10px 10px 20px; }
ol li {  }
p  { margin-top: 10px; }
pre { background: #efefef; border: none; font: 10pt courier,serif; margin: 15px 0; padding: 10px; }
tt { font-size: 10pt; }

/* Controls */
.searchButton { background: #eee; border: 1px solid #ccc; color: #333; font: bold 8pt sans-serif; height: 20px; }

/* Boxes */
.fullbox { border: 1px solid #ccc; margin:5px; }
.title { background: #e8f2f8; border: none; border-bottom: 1px solid #ccc; color: #0e3793; font: bold 14pt sans-serif; margin: 0; padding: 5px; }
.subtitle { font: bold 10pt sans-serif; }
.example { background: #efefef; display: block; margin: 15px 0; padding: 10px; }

/* Formatting */
.clear { clear: both; }
.code { font: 10pt courier,serif; }
.hash { color: #090; }
.content { padding: 10px; }

/* Special elements */
div#kx-linkbar img { margin-right: 20px; }


.row {min-width:90% !important;}
.toctoggle {display:none}

table.wikitable &gt; tr &gt; th, 
table.wikitable &gt; tr &gt;td, 
table.wikitable &gt; * &gt; tr &gt;th, 
table.wikitable &gt; * &gt; tr &gt; td {
padding: 1px;
}
/*
div#viki_0{
width:100% !important;
}*/
.vikijs-detail-panel {
border:none !important;
background:white !important;
font-size:90%;
}
.vikijs-graph-container {
border:none !important;
}
.smwtable .row-even {
	background-color:#FFF;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
.smwtable .row-odd .stripe {
	background-color:#f0f7f8;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
h3#tagline {display:none; }
#footer-privacy {display:none}
#footer-disclaimer {display:none}
#footer-about {display:none}
#footer-lastmod {font-size:70%;}
#footer-viewcount {font-size:70%;}

p.title {
color:#009933;
font-size:100%;
}
h2 {
 font-size:125%;
}

h5 {
color: #666666;
}
.mw-search-formheader  {display:none; }
.thumbinner {
padding-left:5px;
padding-top:5px;
padding-bottom:5px;
}
.thumbcaption {
font-size:100%;
color:#009933;
background: white;
text-align: center;
}

h4 {
color:#009933;
}

form#sfForm.createbox, .formtable, table.formtable tr {
 background-color:#F0F8FF  !important;
}
form#sfForm.createbox, table.formtable tbody tr td table {
border: 1px solid #F0F8FF  !important;
}
option {
    font-weight:normal;
   font-size: x-small;
}
.createboxInput {
       background-color:#FFFFFF  !important;
}
.navbar-item {
	color: white !important;
	font-weight: bold;
	padding-top: 9px;
	padding-right: 10px;
}
.title {
	color:#009933;
        text-align: left;
        font-size:150%;
}

.top-bar,
.top-bar-section ul,
.top-bar-section ul li.active &gt; a,
.top-bar-section li a:not(.button),
.top-bar-section .has-form {
background:#061734;
font-size:90%;
color: #FFFFFF;
}

.top-bar-section &gt; ul &gt; .divider,
.top-bar-section &gt; ul &gt; [role="separator"] {
  border-color: #164eaf;
}

/* Darker color for the hover over items */
.top-bar-section ul li.hover &gt; a,
.top-bar-section ul li ul.dropdown li.hover &gt; a{
    background: #113e8c;
}

/* Slightly darker color for the dropdowns*/ 
.top-bar-section ul li ul.dropdown li &gt; a {
    background: #061734;
}
.spacer {
        height: 30px;
}
.np {
        height: 15px;
}
.hierarchyText {
        font-size:80%;
        font-weight:bold;
        height: 20px;
}
.hierarchyText table tbody tr  {
       background-color: #d5f99b;
       border: 1px solid #BFE08B;
       height: 20px;
}

.examplebread table tbody tr {
 background-color: #ADDFFF;
}

.citationtable {
	border: solid 1px #BBBBBB;
}

.citationtable td {
	padding-left: 5px;
	padding-right: 5px;
	max-width: 600px;
}
.citationtablelong td {
	padding-left: 5px;
	padding-right: 5px;
}

.itemtable td {
	vertical-align: top;
	min-width: 200px;
}

.ratingselected a {
	font-weight: bold;
	color: orange !important;
}

.nowrap {
	white-space: nowrap;
}
.filtered-filters { 
    float: left;
    width: 30%;
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    background: transparent;
}

.filtered-filters .filtered-value .filtered-value-option {
    display: block !important;
    width: 90% !important;
    padding: 0 !important;
}
 
.filtered-views { 
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    max-height: 800px;
}
 
.filtered-views .filtered-list { 
    width: 95% !important;
}
 
.filter_name {
    width: 150px;
    background:#96aab2;
    color:black;
    text-align:left;
    align:left;
    border:1px solid #ddd;
    padding: 3px;
}
 
.filter_value {
    width: 400px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.filter_icon {
    width: 50px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.top-bar.expanded .title-area {
   background:#164eaf;
}

/* CSS placed here will be applied to all skins */
#ca-protect { display: none !important; } 
#ca-delete { display: none !important; } 
#ca-edit { display: none !important; } 
.toc, #toc { display: none; }</text>
    <sha1>8866ed8e90f2413e002c9cab241aeb485cc2e126</sha1>
  </revision>
  <revision>
    <id>189</id>
    <parentid>188</parentid>
    <timestamp>2015-12-31T18:48:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>css</model>
    <format>text/css</format>
    <text bytes="5663" xml:space="preserve">/* CSS placed here will be applied to all skins */

.smwbuiltin a,
.smwbuiltin a.new {
    color: #FF8000;
}

/* CSS placed here will be applied to all skins */

/* MediaWiki overrides */
/* body.page-Main_Page h1.firstHeading { display:none; } */
#footer-info { display: none; } /* Hide footer */
li#ca-talk { display: none; } /* Hide discussion tab */
#pt-login { display: none; } /* Hide login text */
#p-tb { display: none; } /* Hide toolbox */
/* #ca-history { display: none; } /* Hide "View history" */


/* Elements */
code { background: none; font: 10pt courier,serif; }
h2 { margin-top: 15px; }
h3 { color: #222; font-size: 11pt; margin: 10px 0 -5px; }
ol img { display: block; margin: 10px 10px 20px; }
ol li {  }
p  { margin-top: 10px; }
pre { background: #efefef; border: none; font: 10pt courier,serif; margin: 15px 0; padding: 10px; }
tt { font-size: 10pt; }

/* Controls */
.searchButton { background: #eee; border: 1px solid #ccc; color: #333; font: bold 8pt sans-serif; height: 20px; }

/* Boxes */
.fullbox { border: 1px solid #ccc; margin:5px; }
.title { background: #e8f2f8; border: none; border-bottom: 1px solid #ccc; color: #0e3793; font: bold 14pt sans-serif; margin: 0; padding: 5px; }
.subtitle { font: bold 10pt sans-serif; }
.example { background: #efefef; display: block; margin: 15px 0; padding: 10px; }

/* Formatting */
.clear { clear: both; }
.code { font: 10pt courier,serif; }
.hash { color: #090; }
.content { padding: 10px; }

/* Special elements */
div#kx-linkbar img { margin-right: 20px; }


.row {min-width:90% !important;}
.toctoggle {display:none}

table.wikitable &gt; tr &gt; th, 
table.wikitable &gt; tr &gt;td, 
table.wikitable &gt; * &gt; tr &gt;th, 
table.wikitable &gt; * &gt; tr &gt; td {
padding: 1px;
}
/*
div#viki_0{
width:100% !important;
}*/
.vikijs-detail-panel {
border:none !important;
background:white !important;
font-size:90%;
}
.vikijs-graph-container {
border:none !important;
}
.smwtable .row-even {
	background-color:#FFF;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
.smwtable .row-odd .stripe {
	background-color:#f0f7f8;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
h3#tagline {display:none; }
#footer-privacy {display:none}
#footer-disclaimer {display:none}
#footer-about {display:none}
#footer-lastmod {font-size:70%;}
#footer-viewcount {font-size:70%;}

p.title {
color:#009933;
font-size:100%;
}
h2 {
 font-size:125%;
}

h5 {
color: #666666;
}
.mw-search-formheader  {display:none; }
.thumbinner {
padding-left:5px;
padding-top:5px;
padding-bottom:5px;
}
.thumbcaption {
font-size:100%;
color:#009933;
background: white;
text-align: center;
}

h4 {
color:#009933;
}

form#sfForm.createbox, .formtable, table.formtable tr {
 background-color:#F0F8FF  !important;
}
form#sfForm.createbox, table.formtable tbody tr td table {
border: 1px solid #F0F8FF  !important;
}
option {
    font-weight:normal;
   font-size: x-small;
}
.createboxInput {
       background-color:#FFFFFF  !important;
}
.navbar-item {
	color: white !important;
	font-weight: bold;
	padding-top: 9px;
	padding-right: 10px;
}
.title {
	color:#009933;
        text-align: left;
        font-size:150%;
}

.top-bar,
.top-bar-section ul,
.top-bar-section ul li.active &gt; a,
.top-bar-section li a:not(.button),
.top-bar-section .has-form {
background:#061734;
font-size:90%;
color: #FFFFFF;
}

.top-bar-section &gt; ul &gt; .divider,
.top-bar-section &gt; ul &gt; [role="separator"] {
  border-color: #164eaf;
}

/* Darker color for the hover over items */
.top-bar-section ul li.hover &gt; a,
.top-bar-section ul li ul.dropdown li.hover &gt; a{
    background: #113e8c;
}

/* Slightly darker color for the dropdowns*/ 
.top-bar-section ul li ul.dropdown li &gt; a {
    background: #061734;
}
.spacer {
        height: 30px;
}
.np {
        height: 15px;
}
.hierarchyText {
        font-size:80%;
        font-weight:bold;
        height: 20px;
}
.hierarchyText table tbody tr  {
       background-color: #d5f99b;
       border: 1px solid #BFE08B;
       height: 20px;
}

.examplebread table tbody tr {
 background-color: #ADDFFF;
}

.citationtable {
	border: solid 1px #BBBBBB;
}

.citationtable td {
	padding-left: 5px;
	padding-right: 5px;
	max-width: 600px;
}
.citationtablelong td {
	padding-left: 5px;
	padding-right: 5px;
}

.itemtable td {
	vertical-align: top;
	min-width: 200px;
}

.ratingselected a {
	font-weight: bold;
	color: orange !important;
}

.nowrap {
	white-space: nowrap;
}
.filtered-filters { 
    float: left;
    width: 30%;
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    background: transparent;
}

.filtered-filters .filtered-value .filtered-value-option {
    display: block !important;
    width: 90% !important;
    padding: 0 !important;
}
 
.filtered-views { 
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    max-height: 800px;
}
 
.filtered-views .filtered-list { 
    width: 95% !important;
}
 
.filter_name {
    width: 150px;
    background:#96aab2;
    color:black;
    text-align:left;
    align:left;
    border:1px solid #ddd;
    padding: 3px;
}
 
.filter_value {
    width: 400px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.filter_icon {
    width: 50px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.top-bar.expanded .title-area {
   background:#164eaf;
}

/* CSS placed here will be applied to all skins */
#ca-protect { display: none !important; } 
#ca-delete { display: none !important; } 
.toc, #toc { display: none; }</text>
    <sha1>a31fb8cafba941a7c27e425ef344fcd52b77ac54</sha1>
  </revision>
  <revision>
    <id>192</id>
    <parentid>189</parentid>
    <timestamp>2016-01-01T00:09:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>css</model>
    <format>text/css</format>
    <text bytes="7162" xml:space="preserve">/* CSS placed here will be applied to all skins */

.smwbuiltin a,
.smwbuiltin a.new {
    color: #FF8000;
}

/* CSS placed here will be applied to all skins */

/* MediaWiki overrides */
/* body.page-Main_Page h1.firstHeading { display:none; } */
#footer-info { display: none; } /* Hide footer */
li#ca-talk { display: none; } /* Hide discussion tab */
#pt-login { display: none; } /* Hide login text */
#p-tb { display: none; } /* Hide toolbox */
/* #ca-history { display: none; } /* Hide "View history" */


/* Elements */
code { background: none; font: 10pt courier,serif; }
h2 { margin-top: 15px; }
h3 { color: #222; font-size: 11pt; margin: 10px 0 -5px; }
ol img { display: block; margin: 10px 10px 20px; }
ol li {  }
p  { margin-top: 10px; }
pre { background: #efefef; border: none; font: 10pt courier,serif; margin: 15px 0; padding: 10px; }
tt { font-size: 10pt; }

/* Controls */
.searchButton { background: #eee; border: 1px solid #ccc; color: #333; font: bold 8pt sans-serif; height: 20px; }

/* Boxes */
.fullbox { border: 1px solid #ccc; margin:5px; }
.title { background: #e8f2f8; border: none; border-bottom: 1px solid #ccc; color: #0e3793; font: bold 14pt sans-serif; margin: 0; padding: 5px; }
.subtitle { font: bold 10pt sans-serif; }
.example { background: #efefef; display: block; margin: 15px 0; padding: 10px; }

/* Formatting */
.clear { clear: both; }
.code { font: 10pt courier,serif; }
.hash { color: #090; }
.content { padding: 10px; }

/* Special elements */
div#kx-linkbar img { margin-right: 20px; }


.row {min-width:90% !important;}
.toctoggle {display:none}

table.wikitable &gt; tr &gt; th, 
table.wikitable &gt; tr &gt;td, 
table.wikitable &gt; * &gt; tr &gt;th, 
table.wikitable &gt; * &gt; tr &gt; td {
padding: 1px;
}
/*
div#viki_0{
width:100% !important;
}*/
.vikijs-detail-panel {
border:none !important;
background:white !important;
font-size:90%;
}
.vikijs-graph-container {
border:none !important;
}
.smwtable .row-even {
	background-color:#FFF;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
.smwtable .row-odd .stripe {
	background-color:#f0f7f8;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
h3#tagline {display:none; }
#footer-privacy {display:none}
#footer-disclaimer {display:none}
#footer-about {display:none}
#footer-lastmod {font-size:70%;}
#footer-viewcount {font-size:70%;}

p.title {
color:#009933;
font-size:100%;
}
h2 {
 font-size:125%;
}

h5 {
color: #666666;
}
.mw-search-formheader  {display:none; }
.thumbinner {
padding-left:5px;
padding-top:5px;
padding-bottom:5px;
}
.thumbcaption {
font-size:100%;
color:#009933;
background: white;
text-align: center;
}

h4 {
color:#009933;
}

form#sfForm.createbox, .formtable, table.formtable tr {
 background-color:#F0F8FF  !important;
}
form#sfForm.createbox, table.formtable tbody tr td table {
border: 1px solid #F0F8FF  !important;
}
option {
    font-weight:normal;
   font-size: x-small;
}
.createboxInput {
       background-color:#FFFFFF  !important;
}
.navbar-item {
	color: white !important;
	font-weight: bold;
	padding-top: 9px;
	padding-right: 10px;
}
.title {
	color:#009933;
        text-align: left;
        font-size:150%;
}

.top-bar,
.top-bar-section ul,
.top-bar-section ul li.active &gt; a,
.top-bar-section li a:not(.button),
.top-bar-section .has-form {
background:#061734;
font-size:90%;
color: #FFFFFF;
}

.top-bar-section &gt; ul &gt; .divider,
.top-bar-section &gt; ul &gt; [role="separator"] {
  border-color: #164eaf;
}

/* Darker color for the hover over items */
.top-bar-section ul li.hover &gt; a,
.top-bar-section ul li ul.dropdown li.hover &gt; a{
    background: #113e8c;
}

/* Slightly darker color for the dropdowns*/ 
.top-bar-section ul li ul.dropdown li &gt; a {
    background: #061734;
}
.spacer {
        height: 30px;
}
.np {
        height: 15px;
}
.hierarchyText {
        font-size:80%;
        font-weight:bold;
        height: 20px;
}
.hierarchyText table tbody tr  {
       background-color: #d5f99b;
       border: 1px solid #BFE08B;
       height: 20px;
}

.examplebread table tbody tr {
 background-color: #ADDFFF;
}

.citationtable {
	border: solid 1px #BBBBBB;
}

.citationtable td {
	padding-left: 5px;
	padding-right: 5px;
	max-width: 600px;
}
.citationtablelong td {
	padding-left: 5px;
	padding-right: 5px;
}

.itemtable td {
	vertical-align: top;
	min-width: 200px;
}

.ratingselected a {
	font-weight: bold;
	color: orange !important;
}

.nowrap {
	white-space: nowrap;
}
.filtered-filters { 
    float: left;
    width: 30%;
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    background: transparent;
}

.filtered-filters .filtered-value .filtered-value-option {
    display: block !important;
    width: 90% !important;
    padding: 0 !important;
}
 
.filtered-views { 
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    max-height: 800px;
}
 
.filtered-views .filtered-list { 
    width: 95% !important;
}
 
.filter_name {
    width: 150px;
    background:#96aab2;
    color:black;
    text-align:left;
    align:left;
    border:1px solid #ddd;
    padding: 3px;
}
 
.filter_value {
    width: 400px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.filter_icon {
    width: 50px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.top-bar.expanded .title-area {
   background:#164eaf;
}

/* CSS placed here will be applied to all skins */
#ca-protect { display: none !important; } 
#ca-delete { display: none !important; } 
.toc, #toc { display: none; }

/**
 * SECTION: SMW-Style Infoboxes
 *
 * Many "infoboxes" (not using Template:Infobox) have/had the CSS below
 * manually entered into each table. This was the case in Template:Award
 * and Template:Person. Now, instead, those "infoboxes" simply list class=
 * "smw-style-infobox-table" because this type of "infobox" is similar to 
 * what is used by SemanticMediaWiki and SemanticForms
 **/
.smw-style-infobox-table {
    width:            20em;
    font-size:        90%;
    border:           1px solid #aaaaaa;
    background-color: #f9f9f9;
    color:            black;
    margin-bottom:    0.5em;
    margin-left:      1em;
    padding:          0.2em;
    float:            right;
    clear:            right;
    text-align:       left;
    font-size:        92%;
}
.smw-style-infobox-table tr {
    vertical-align: top;
}
 
.smw-style-infobox-table-header {
    text-align:       center;
    background-color: #ccccff;
    font-size:        15px;
}
/**
 * END SECTION: SMW-Style Infoboxes
 **/

.agenda {
   text-align: left;
}
.agenda th {
   border: 1px solid #555555;
   background-color: #eeeeee;
   text-align: center;
   font-size: 120%;
}
.agenda td {
   border: 1px solid #555555;
   padding: 10px;
   vertical-align: top;
}

/* Float Left-Right-Center */
.chart-float-right {
	float:right;
	margin-left:10px;
	margin-bottom:10px;
	clear:both;
}
 
.chart-float-left {
	margin-left:0px;
	margin-right:10px;
	float:left;
	clear:both;
}
 
.chart-center {
	display: inline-block;
}</text>
    <sha1>4128bf566fde2feca6d67d6053d95ea5f48abe07</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>Property:Has interest</title>
  <ns>102</ns>
  <id>70</id>
  <revision>
    <id>190</id>
    <timestamp>2015-12-31T23:14:06Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Page]].</text>
    <sha1>a77920a9d24db1d24320cdd74718a3bf351bd0c9</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>Property:Parent related article</title>
  <ns>102</ns>
  <id>71</id>
  <revision>
    <id>191</id>
    <timestamp>2015-12-31T23:16:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Page]].</text>
    <sha1>a77920a9d24db1d24320cdd74718a3bf351bd0c9</sha1>
  </revision>
</page>
<page arvcontinue="20151229115752|144">
  <title>CCOD</title>
  <ns>0</ns>
  <id>72</id>
  <revision>
    <id>193</id>
    <timestamp>2016-01-01T03:00:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "== CCOD Best Practices and Lessons Learned ==  These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2)..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8018" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.
{{New Paragrah}}
Favor the small and reusable: Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.
Make components discoverable: Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.
{{New Paragraph}}
Develop components with an understanding of the end user: Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:
Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
{{New Paragraph}}
Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).
{{New Paragraph}}
Strongly consider RESTful architectures: This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.
{{New Paragraph}}
Strongly consider loose couplers: Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:

*UCore for mission data interoperability [4]

*KML for geo-referenced data [5]

*WADL for RESTful services

*CoT for tactical mission data interoperability [6]

 Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

 Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).
{{New Paragraph}}
Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.
{{New Paragraph}}
Emphasize documentation: Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. 
Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.
{{New Paragraph}}
Separate visualization from function: One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.
{{New Paragraph}}
Accommodate dependencies: There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.
{{New Paragraph}}
Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.
{{New Paragraph}}
Seek operational context: Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).
&lt;br /&gt;
'''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.
&lt;br /&gt;
'''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>4da3aa0db00279d84801c628c07ce18d9d79c89a</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>CCOD</title>
  <ns>0</ns>
  <id>72</id>
  <revision>
    <id>194</id>
    <parentid>193</parentid>
    <timestamp>2016-01-01T03:12:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7895" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.
&lt;br /&gt;
'''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.
Make components discoverable: Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.
&lt;br /&gt;
'''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:
* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).
&lt;br /&gt;
'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.
&lt;br /&gt;
'''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:

*UCore for mission data interoperability [4]

*KML for geo-referenced data [5]

*WADL for RESTful services

*CoT for tactical mission data interoperability [6]

&lt;br /&gt;
Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).
* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* Emphasize documentation: Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. 
Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* Separate visualization from function: One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* Accommodate dependencies: There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* Seek operational context: Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>b8f644443fbbf7743ec0fd507736671eb6e1cb3c</sha1>
  </revision>
  <revision>
    <id>195</id>
    <parentid>194</parentid>
    <timestamp>2016-01-01T03:16:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7957" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.
&lt;br /&gt;
'''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.
Make components discoverable: Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.
&lt;br /&gt;
'''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:
* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
&lt;br /&gt;
* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).
&lt;br /&gt;
'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.
&lt;br /&gt;
'''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:

*UCore for mission data interoperability [4]

*KML for geo-referenced data [5]

*WADL for RESTful services

*CoT for tactical mission data interoperability [6]

&lt;br /&gt;
Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).
&lt;br /&gt;
* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.
&lt;br /&gt;
* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. 
Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.
&lt;br /&gt;
* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.
&lt;br /&gt;
* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.
&lt;br /&gt;
* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>a29d324dc7109816ab5b4e21c5ab4faab9ec1955</sha1>
  </revision>
  <revision>
    <id>196</id>
    <parentid>195</parentid>
    <timestamp>2016-01-01T03:16:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7950" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.
&lt;br /&gt;
'''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.
Make components discoverable: Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.
&lt;br /&gt;
'''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:
* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).
&lt;br /&gt;
'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.
&lt;br /&gt;
'''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:

*UCore for mission data interoperability [4]

*KML for geo-referenced data [5]

*WADL for RESTful services

*CoT for tactical mission data interoperability [6]

&lt;br /&gt;
Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).
&lt;br /&gt;
* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.
&lt;br /&gt;
* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. 
Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.
&lt;br /&gt;
* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.
&lt;br /&gt;
* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.
&lt;br /&gt;
* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>ce1fac4467b417d55fc0e8063f7794c48557203d</sha1>
  </revision>
  <revision>
    <id>197</id>
    <parentid>196</parentid>
    <timestamp>2016-01-01T03:18:49Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7936" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.
&lt;br /&gt;
'''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.
Make components discoverable: Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.
&lt;br /&gt;
'''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:
* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).
&lt;br /&gt;
'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.
&lt;br /&gt;
'''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
*UCore for mission data interoperability 
*KML for geo-referenced data 
*WADL for RESTful services
*CoT for tactical mission data interoperability 
&lt;br /&gt;
Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).
&lt;br /&gt;
* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.
&lt;br /&gt;
* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. 
Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.
&lt;br /&gt;
* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.
&lt;br /&gt;
* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.
&lt;br /&gt;
* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>8d70c14788678d9aa43bd2a573dc1dd26e256e56</sha1>
  </revision>
  <revision>
    <id>198</id>
    <parentid>197</parentid>
    <timestamp>2016-01-01T03:22:45Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7906" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.
&lt;br /&gt;
'''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.
Make components discoverable: Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.
&lt;br /&gt;
'''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:
* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).
&lt;br /&gt;
'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.
&lt;br /&gt;
'''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
*UCore for mission data interoperability 
*KML for geo-referenced data 
*WADL for RESTful services
*CoT for tactical mission data interoperability 

Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).
&lt;br /&gt;
* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. 
Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>f8d31abb5396e67de0706511ca9a3a076706c651</sha1>
  </revision>
  <revision>
    <id>199</id>
    <parentid>198</parentid>
    <timestamp>2016-01-01T03:26:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7907" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.

'''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.

'''Make components discoverable''': Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.
&lt;br /&gt;
'''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:
* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).
&lt;br /&gt;
'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.
&lt;br /&gt;
'''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
*UCore for mission data interoperability 
*KML for geo-referenced data 
*WADL for RESTful services
*CoT for tactical mission data interoperability 

Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).
&lt;br /&gt;
* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. 
Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>033dfda1a6630a64a2a8ce039c992674d8663d4d</sha1>
  </revision>
  <revision>
    <id>200</id>
    <parentid>199</parentid>
    <timestamp>2016-01-01T03:27:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7906" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.

'''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.

'''Make components discoverable''': Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.
&lt;br /&gt;
'''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:
* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).
&lt;br /&gt;
'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.
&lt;br /&gt;
'''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
*UCore for mission data interoperability 
*KML for geo-referenced data 
*WADL for RESTful services
*CoT for tactical mission data interoperability 

Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).
&lt;br /&gt;
* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>cb5ab9ef07f1cb7b0f3db7756909fea5249ce663</sha1>
  </revision>
  <revision>
    <id>201</id>
    <parentid>200</parentid>
    <timestamp>2016-01-01T03:32:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7910" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.

* '''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.

* '''Make components discoverable''': Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.

* '''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:

 * Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
 * Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).
&lt;br /&gt;
*'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.
&lt;br /&gt;
* '''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
 *UCore for mission data interoperability 
 *KML for geo-referenced data 
 *WADL for RESTful services
 *CoT for tactical mission data interoperability 

Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).

* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>6229c474dc18410f81e07f46daae4118574f956e</sha1>
  </revision>
  <revision>
    <id>202</id>
    <parentid>201</parentid>
    <timestamp>2016-01-01T03:34:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7908" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.

* '''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.

* '''Make components discoverable''': Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.

* '''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:

* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).
&lt;br /&gt;
*'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.
&lt;br /&gt;
* '''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
 *UCore for mission data interoperability 
 *KML for geo-referenced data 
 *WADL for RESTful services
 *CoT for tactical mission data interoperability 

Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).

* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>3e4037234484f09f511949ea62a6f4fcf38fcb4d</sha1>
  </revision>
  <revision>
    <id>203</id>
    <parentid>202</parentid>
    <timestamp>2016-01-01T03:36:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7896" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.

* '''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.

* '''Make components discoverable''': Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.

* '''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:

* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).

*'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.

* '''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
 *UCore for mission data interoperability 
 *KML for geo-referenced data 
 *WADL for RESTful services
 *CoT for tactical mission data interoperability 

Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).

* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.</text>
    <sha1>5b9cae889f17e6e89c581b8e2ea1dcd3fbc07f2d</sha1>
  </revision>
  <revision>
    <id>204</id>
    <parentid>203</parentid>
    <timestamp>2016-01-01T03:39:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8000" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.

* '''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.

* '''Make components discoverable''': Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.

* '''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:

* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.
* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.
* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).

*'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.

* '''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
 *UCore for mission data interoperability 
 *KML for geo-referenced data 
 *WADL for RESTful services
 *CoT for tactical mission data interoperability 

Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).

* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: CCOD Best Practices }}
{{#set:Title Icon=Target-icon.png}}</text>
    <sha1>5d782508f0926190b6e8fad45b568ad4fd4ccf5a</sha1>
  </revision>
  <revision>
    <id>205</id>
    <parentid>204</parentid>
    <timestamp>2016-01-01T03:43:31Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8002" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.

* '''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.

* '''Make components discoverable''': Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.

* '''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:

* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.

* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.

* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).

*'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard [3], which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.

* '''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
 *UCore for mission data interoperability 
 *KML for geo-referenced data 
 *WADL for RESTful services
 *CoT for tactical mission data interoperability 

Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* Explicitly design component granularity: Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).

* Prepare design/artifacts and integration plan early to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* Scope the use of CCOD: CCOD represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: CCOD Best Practices }}
{{#set:Title Icon=Target-icon.png}}</text>
    <sha1>3844b16a1daf24c1a029860cfe0f8a39cecbe79e</sha1>
  </revision>
  <revision>
    <id>206</id>
    <parentid>205</parentid>
    <timestamp>2016-01-01T03:48:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8015" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.

* '''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.

* '''Make components discoverable''': Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.

* '''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:

* Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.

* Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.

* Commander is a high-level information consumer who combines data from a number of sources to make final decisions.
Focus on reuse: Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).

*'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.

* '''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
# UCore for mission data interoperability 
# KML for geo-referenced data 
# WADL for RESTful services
# CoT for tactical mission data interoperability 

Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* '''Explicitly design component granularity''': Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).

* '''Prepare design/artifacts and integration plan early''' to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* '''Scope the use of CCOD: CCOD''' represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: CCOD Best Practices }}
{{#set:Title Icon=Target-icon.png}}</text>
    <sha1>c478a9096f34ae2fa278dc4c9b18cbd1f820ef9d</sha1>
  </revision>
  <revision>
    <id>207</id>
    <parentid>206</parentid>
    <timestamp>2016-01-01T03:50:41Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8027" xml:space="preserve">== CCOD Best Practices and Lessons Learned ==

These lessons have been derived from hands-on CCOD prototyping and operator-centric analyses of current Command and Control (C2) systems and workarounds, filtered through the lens of practiced distributed computing expertise. However, it should be emphasized that CCOD is still a budding concept, and these lessons are still forming.

* '''Favor the small and reusable''': Using Occam's razor, where there is a choice between developing or using two or more components; usually, the small simpler one is preferred. A component should be "light weight" to ensure its ease of adoption and integration across a variety of users and uses.

* '''Make components discoverable''': Ad-hoc mission-focused composability necessitates the ability to find the components and data best suited for a particular task in timely manner. A "marketplace" or "app store" concept is a useful construct for many CCOD environments.

* '''Develop components with an understanding of the end user''': Early experience is leaning toward a design concept for CCOD that follows a multi-level producer/consumer design pattern. Some components will still be developed/composed by an engineer with operational/domain knowledge, but ultimately the promise of CCOD is fulfilled by the user/operator composing new functionality from existing components. Throughout the composition and use process, there are a number of users with differing roles and responsibilities:

 * Combat Coder or "Mashup Engineer" develops, prepares, and publishes the data and services for consumption. This engineer has operational/domain knowledge and can compose data and visualizations into raw application components for users.

 * Average users/operators tailor the raw application components to meet their specific needs, responsibilities, and preferences. This is the first layer of users who consume or interpret the data, potentially adding, modifying, or filtering it before sending it up the chain. This is a typical operator in a mission setting who has potentially complex, mission-centric responsibilities yet is not a computer programmer.

 * Commander is a high-level information consumer who combines data from a number of sources to make final decisions.

* '''Focus on reuse''': Perhaps the greatest value of composable capability is the reuse of someone else's components and compositions. Each CCOD component should be reusable and generic allowing other CCOD projects to use it, particularly outside the direct composition environment. Each solution should be used by successive CCOD projects to build on previous experience and lessons learned. Where possible, use existing open source solutions/tools that have adoption momentum and are adequate to the task at hand (e.g., Restlet, PostgreSQL, PostGIS, Smile, Jetty).

*'''Strongly consider RESTful architectures''': This framework has proven to be robust and flexible enough to allow for quick development and integration of components. Consider the Web Application Description Language (WADL) data standard which has been used to facilitate communication between RESTful services. While WADLs have some potential restrictions as a result of their simplicity, these restrictions were not a hindrance in a Department of Defense project using CCOD. In fact, it was an advantage to the implemented architecture. WADLs are intuitive, easy to write and understand, and require minimal effort for cross-service communication.

* '''Strongly consider loose couplers''': Design components and services to be independent of one another through use of loose couplers. In some MITRE CCOD projects, effective loose couplers proved to be:
# UCore for mission data interoperability 
# KML for geo-referenced data 
# WADL for RESTful services
# CoT for tactical mission data interoperability 

Use standard industry data formats as loose couplers for ease of reuse, integration, and adoption of components. Loose couplers can reduce the number of required data translations from N2 to 2N.

* '''Explicitly design component granularity''': Components of a composition must be at the appropriate abstraction level. For non-technical users to perform composition, the components must be abstract enough to be understood, flexible, and unusable. Minimize interaction between the components by using a loose coupler. Document dependencies between components/services. It is important to test the component abstraction level with the intended user population (e.g., average user, combat coder, etc.).

* '''Prepare design/artifacts and integration plan early''' to mitigate integration challenges: Due to the challenge of integrating diverse components at run-time, it is important to develop system architecture and sequence diagrams in the early stages of a CCOD project. This helps build a strong foundation when later creating an integrated system. Where possible, use approved design patterns to enhance extensibility and understanding. It is important to clearly communicate the design and goal of the various project elements to the project team early in the process. It is important to have lower-level component tests along the way, to test each self-contained component, as well as enterprise-scope testing. Incorporate many iterations, with small increments to functionality, to enable testing.

* '''Emphasize documentation''': Documentation is crucial for any system implementing CCOD principles. The goal is to have combat coders and average users who may be unfamiliar with any component/service leverage or reuse this functionality. Document early on and throughout the development process, and provide easy discovery and navigation of the documentation. Agree upon the documentation approach at the beginning of the project. As appropriate, use tools and formal modeling approaches to ease communication outside the project.

* '''Separate visualization from function''': One CCOD-based prototype developed at MITRE could not naturally conform to a typical Model-View-Controller (MVC) design pattern, yet separation of the visualization from data components remained critical. Data only has to be exposed in simple standards to be visualized in useful ways. These include Hypertext Markup Language (HTML) tables, Extensible Markup Language (XML) (plain, Real Simple Syndication [RSS], geoRSS, KML, RESTful Web services), comma-separated values, etc.

* '''Accommodate dependencies''': There is greater dependence and reliance on other systems' performance and availability in a CCOD system. If there are known performance issues, it is advisable to duplicate data sources, where possible, so that no piece of the system is completely dependent on an unreliable component. Document dependencies using a modeling paradigm as appropriate.

* '''Scope the use of CCOD: CCOD''' represents a very large solution space. It is important to have a well-defined use case for CCOD that can be scoped within given resource and time restrictions.

* '''Seek operational context''': Seek operational expertise early to define the operational scenarios and use cases to which a CCOD solution will be applied. Some use cases, situations, or entire systems may not be viable candidates for a CCOD approach (e.g., real-time semi-automated targeting systems).

* '''Build from existing components''': Where possible, CCOD will provide capabilities built out of existing components discoverable and integratable on the network and/or adaptors interfacing with "non-composable" systems of record. Seek ways to provide composable "pieces" of large systems.

* '''Verification/Validation''': All components should be tested to ensure that they operate as designed, prior to being integrated into the component repository or storefront. Developer testing should be documented so that users of components will be able to better understand the approved use and limitations of components.

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: CCOD Best Practices }}
{{#set:Title Icon=Target-icon.png}}</text>
    <sha1>b8f14c46672420313d01fa59ae276722321505e9</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:Translatable template name</title>
  <ns>10</ns>
  <id>82</id>
  <revision>
    <id>335</id>
    <parentid>220</parentid>
    <timestamp>2016-01-02T11:02:56Z</timestamp>
    <contributor>
      <username>Kaganer</username>
      <id>0</id>
    </contributor>
    <comment>namespace &gt;&gt; tntns</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="314" xml:space="preserve">&lt;includeonly&gt;{{#invoke:Template translation{{{sandbox|}}}|getTranslatedTemplate|uselang={{{uselang|}}}|tntns={{{tntns|{{{namespace|}}}}}}|template={{#if:{{{noshift|}}}|{{{template}}}|{{{1}}}}}|noshift={{{noshift|}}}&lt;!-- there are no other parameters here --&gt;}}&lt;/includeonly&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>cf01b803bccfc7ef72e324dc96840b2d093194a4</sha1>
  </revision>
  <revision>
    <id>220</id>
    <timestamp>2016-01-06T06:11:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;includeonly&gt;{{#invoke:Template translation{{{sandbox|}}}|getTranslatedTemplate|uselang={{{uselang|}}}|tntns={{{tntns|{{{namespace|}}}}}}|template={{#if:{{{noshift|}}}|{{{temp..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="314" xml:space="preserve">&lt;includeonly&gt;{{#invoke:Template translation{{{sandbox|}}}|getTranslatedTemplate|uselang={{{uselang|}}}|tntns={{{tntns|{{{namespace|}}}}}}|template={{#if:{{{noshift|}}}|{{{template}}}|{{{1}}}}}|noshift={{{noshift|}}}&lt;!-- there are no other parameters here --&gt;}}&lt;/includeonly&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>cf01b803bccfc7ef72e324dc96840b2d093194a4</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:Navbar</title>
  <ns>10</ns>
  <id>99</id>
  <revision>
    <id>287</id>
    <parentid>240</parentid>
    <timestamp>2016-01-03T04:40:07Z</timestamp>
    <contributor>
      <username>Shirayuki</username>
      <id>0</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1087" xml:space="preserve">&lt;span class="noprint plainlinks navbar" style="{{{style|}}}"&gt;&lt;small&gt;&lt;!--

--&gt;{{#if:{{{mini|}}}{{{plain|}}}|&lt;!--nothing--&gt;|&lt;!--else:
--&gt;&lt;span style="{{{fontstyle|}}}"&gt;{{{text|This box:}}} &lt;/span&gt;}}&lt;!--

--&gt;{{#if:{{{brackets|}}}|&lt;span style="{{{fontstyle|}}}"&gt;&amp;#91;&lt;/span&gt;}}&lt;!--

--&gt;&lt;span style="white-space:nowrap;word-spacing:-.12em;"&gt;&lt;!--
--&gt;[[{{ns:10}}:{{{1}}}|&lt;span style="{{{fontstyle|}}}" title="View this template"&gt;&lt;!--
--&gt;{{#if:{{{mini|}}}|v|view}}&lt;/span&gt;]]&lt;!--

--&gt;&lt;span style="{{{fontstyle|}}}"&gt;&amp;#32;&lt;b&gt;&amp;middot;&lt;/b&gt;&amp;#32;&lt;/span&gt;&lt;!--
--&gt;[[{{ns:11}}:{{{1}}}|&lt;span style="{{{fontstyle|}}}" title="Discuss this template"&gt;&lt;!--
--&gt;{{#if:{{{mini|}}}|d|talk}}&lt;/span&gt;]]&lt;!--

--&gt;{{#if:{{{noedit|}}}|&lt;!--nothing--&gt;|&lt;!--else:
--&gt;&lt;span style="{{{fontstyle|}}}"&gt;&amp;#32;&lt;b&gt;&amp;middot;&lt;/b&gt;&amp;#32;&lt;/span&gt;&lt;!--
--&gt;[{{fullurl:{{ns:10}}:{{{1}}}|action=edit}} &lt;span style="{{{fontstyle|}}}" title="Edit this template"&gt;&lt;!--
--&gt;{{#if:{{{mini|}}}|e|edit}}&lt;/span&gt;]}}&lt;!--
--&gt;&lt;/span&gt;&lt;!--

--&gt;{{#if:{{{brackets|}}}|&lt;span style="{{{fontstyle|}}}"&gt;&amp;#93;&lt;/span&gt;}}&lt;!--

--&gt;&lt;/small&gt;&lt;/span&gt;
&lt;noinclude&gt;{{doc}}&lt;/noinclude&gt;</text>
    <sha1>08cf4451d76bbca3ac4337d6976839bb230b2c9a</sha1>
  </revision>
  <revision>
    <id>240</id>
    <timestamp>2016-01-06T06:51:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;span class="noprint plainlinks navbar" style="{{{style|}}}"&gt;&lt;small&gt;&lt;!--  --&gt;{{#if:{{{mini|}}}{{{plain|}}}|&lt;!--nothing--&gt;|&lt;!--else: --&gt;&lt;span style="{{{fontstyle|}}}"&gt;{{{text|T..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1087" xml:space="preserve">&lt;span class="noprint plainlinks navbar" style="{{{style|}}}"&gt;&lt;small&gt;&lt;!--

--&gt;{{#if:{{{mini|}}}{{{plain|}}}|&lt;!--nothing--&gt;|&lt;!--else:
--&gt;&lt;span style="{{{fontstyle|}}}"&gt;{{{text|This box:}}} &lt;/span&gt;}}&lt;!--

--&gt;{{#if:{{{brackets|}}}|&lt;span style="{{{fontstyle|}}}"&gt;&amp;#91;&lt;/span&gt;}}&lt;!--

--&gt;&lt;span style="white-space:nowrap;word-spacing:-.12em;"&gt;&lt;!--
--&gt;[[{{ns:10}}:{{{1}}}|&lt;span style="{{{fontstyle|}}}" title="View this template"&gt;&lt;!--
--&gt;{{#if:{{{mini|}}}|v|view}}&lt;/span&gt;]]&lt;!--

--&gt;&lt;span style="{{{fontstyle|}}}"&gt;&amp;#32;&lt;b&gt;&amp;middot;&lt;/b&gt;&amp;#32;&lt;/span&gt;&lt;!--
--&gt;[[{{ns:11}}:{{{1}}}|&lt;span style="{{{fontstyle|}}}" title="Discuss this template"&gt;&lt;!--
--&gt;{{#if:{{{mini|}}}|d|talk}}&lt;/span&gt;]]&lt;!--

--&gt;{{#if:{{{noedit|}}}|&lt;!--nothing--&gt;|&lt;!--else:
--&gt;&lt;span style="{{{fontstyle|}}}"&gt;&amp;#32;&lt;b&gt;&amp;middot;&lt;/b&gt;&amp;#32;&lt;/span&gt;&lt;!--
--&gt;[{{fullurl:{{ns:10}}:{{{1}}}|action=edit}} &lt;span style="{{{fontstyle|}}}" title="Edit this template"&gt;&lt;!--
--&gt;{{#if:{{{mini|}}}|e|edit}}&lt;/span&gt;]}}&lt;!--
--&gt;&lt;/span&gt;&lt;!--

--&gt;{{#if:{{{brackets|}}}|&lt;span style="{{{fontstyle|}}}"&gt;&amp;#93;&lt;/span&gt;}}&lt;!--

--&gt;&lt;/small&gt;&lt;/span&gt;
&lt;noinclude&gt;{{doc}}&lt;/noinclude&gt;</text>
    <sha1>08cf4451d76bbca3ac4337d6976839bb230b2c9a</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>MediaWiki:Sf formedit edittitle</title>
  <ns>8</ns>
  <id>73</id>
  <revision>
    <id>208</id>
    <timestamp>2016-01-05T20:31:03Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Edit {{#semantic-title:$2}}"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="27" xml:space="preserve">Edit {{#semantic-title:$2}}</text>
    <sha1>1ac9be958821ef3e718b9ddaeb7787458b5f9983</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Category:Hardening Guides</title>
  <ns>14</ns>
  <id>74</id>
  <revision>
    <id>209</id>
    <timestamp>2016-01-06T02:18:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This is the Hardening Guides category."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38" xml:space="preserve">This is the Hardening Guides category.</text>
    <sha1>28f91b52e30219c21b6112d0ee32229bde3f8c52</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Property:System</title>
  <ns>102</ns>
  <id>75</id>
  <revision>
    <id>210</id>
    <timestamp>2016-01-06T02:59:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Property:Date Issued</title>
  <ns>102</ns>
  <id>76</id>
  <revision>
    <id>211</id>
    <timestamp>2016-01-06T03:07:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Date]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Date]].</text>
    <sha1>5263c8921631f25051f416df19a72490a588561e</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Property:Data Classification</title>
  <ns>102</ns>
  <id>77</id>
  <revision>
    <id>212</id>
    <timestamp>2016-01-06T03:08:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Code]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Code]].</text>
    <sha1>6f45f32988880c7b04366a0b6d289e6358daddd8</sha1>
  </revision>
  <revision>
    <id>213</id>
    <parentid>212</parentid>
    <timestamp>2016-01-06T03:09:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="129" xml:space="preserve">This is a property of type [[Has type::Text]].

[[Allows value::Public]]
[[Allows value::Confidential]]
[[Allows Value::Private]]</text>
    <sha1>059a54240078d6dc9a1e9011df1dc815941273a9</sha1>
  </revision>
  <revision>
    <id>214</id>
    <parentid>213</parentid>
    <timestamp>2016-01-06T03:10:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="103" xml:space="preserve">This is a property of type [[Has type::Text]].

[[Allows value::Public]]
[[Allows value::Confidential]]</text>
    <sha1>faa27fdea90e472c063f7158487a22be0b4b484b</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:System Hardening Guide</title>
  <ns>10</ns>
  <id>78</id>
  <revision>
    <id>215</id>
    <timestamp>2016-01-06T03:11:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "System Hardening Guide" template. It should be called in the following format: &lt;pre&gt; {{System Hardening Guide |Title= |System= |Company Name= |Classif..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="640" xml:space="preserve">&lt;noinclude&gt;
This is the "System Hardening Guide" template.
It should be called in the following format:
&lt;pre&gt;
{{System Hardening Guide
|Title=
|System=
|Company Name=
|Classification=
|Date Issued=
|Review Date=
|Related to=
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
! Title
| [[Full Title::{{{Title|}}}]] 
|-
! System
| {{{System|}}}
|-
! Company Name
| {{{Company Name|}}}
|-
! Classification
| {{{Classification|}}}
|-
! Date Issued
| {{{Date Issued|}}}
|-
! Review Date
| {{{Review Date|}}}
|-
! Related to
| [[Related to::{{{Related to|}}}]] 
|}

[[Category:Guides]]
&lt;/includeonly&gt;</text>
    <sha1>a3172317d2029f51939949366693fd58eeb5269b</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Property:Exif data</title>
  <ns>102</ns>
  <id>79</id>
  <revision>
    <id>216</id>
    <timestamp>2016-01-06T05:23:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Page]].</text>
    <sha1>a77920a9d24db1d24320cdd74718a3bf351bd0c9</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:Extension</title>
  <ns>10</ns>
  <id>80</id>
  <revision>
    <id>217</id>
    <timestamp>2016-01-06T06:08:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Extension" template. It should be called in the following format: &lt;pre&gt; {{Extension }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;inc..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="222" xml:space="preserve">&lt;noinclude&gt;
This is the "Extension" template.
It should be called in the following format:
&lt;pre&gt;
{{Extension
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>b44a5371885e61528b3df5a60ab9812867fc081f</sha1>
  </revision>
  <revision>
    <id>218</id>
    <parentid>217</parentid>
    <timestamp>2016-01-06T06:09:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14112" xml:space="preserve">&lt;includeonly&gt;{{#if: {{{phabricator|}}} | {{ {{TNTN|Ptag}} |{{{phabricator}}}}} }}
{| class="tpl-infobox ext-infobox ext-status-{{#switch: {{lc: {{{status|unknown}}} }}
|unmaintained|archive|milestone|unstable|experimental|beta|stable|magic={{{status}}}
|#default=unknown
}}" cellspacing="0"
|+ '''[[Special:MyLanguage/Manual:Extensions|MediaWiki extensions manual]]'''
|- class="tpl-infobox-header ext-infobox-header"
! colspan="2" style="padding-top: 0.5em;" | [[File:{{#ifeq: {{{status|}}} |unstable|Crystal Clear app error.png|&lt;!--else--&gt;Crystal Clear action run.png}}|link=:Special:MyLanguage/Template:Extension#Content|left|40px]] &lt;span style="font-size: 130%;"&gt;{{{name|{{PAGENAME}}}}}&lt;/span&gt;&lt;br /&gt;
[[Extension status|Release status:]] {{#switch: {{lc: {{{status|unknown}}} }}
|unmaintained|archive|milestone|unstable|experimental|beta|stable|magic={{{status}}}
|#default=unknown
}}&lt;!-- Category logic --&gt;{{#if:{{{license|}}}|{{#ifeq:{{{templatemode|}}}|nocats|&lt;!-- do nothing --&gt;|&lt;!--else--&gt;{{#invoke:Extension|getLicenseCategory|{{{license}}}}}}}}}&lt;!--
--&gt;{{#ifeq:{{{templatemode|}}}|nocats|&lt;!-- do nothing --&gt;|&lt;!--else--&gt;[[Category:{{#switch: {{lc:{{{status|}}} }}
|unstable|experimental|stable = {{{status}}} extensions
|beta = beta status extensions
|unknown = extensions with unknown status
|unmaintained = Not LTS ready
|archive = archive extensions
|milestone = milestone extensions
|#default = extensions with invalid status
}}{{translation}}]]}}
|-
{{#if:{{{image|}}}|
{{!}} colspan="2" style="text-align: center;" {{!}} [[Image:{{{image}}}|{{{imagesize|220}}}px]]
{{!}}-
|{{#if:{{#translation:}}||[[Category:MediaWiki extensions without a screenshot]]}}}}
{{#if:{{{type|}}}{{{type1|}}}|
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#type|'''Implementation''']]
{{!}} {{#invoke:Extension|getTypes}}&lt;!--
--&gt;|&lt;!--else--&gt;&lt;!--
   --&gt;{{#ifeq:{{{templatemode|}}}|nocats|&lt;!--
      nothing
   --&gt;|&lt;!--else--&gt;&lt;!--
      --&gt;{{#invoke:Extension|getType|_missing_}}&lt;!--
   --&gt;}}&lt;!--
--&gt;
{{!}}-
}}
|-
{{#if:{{{description|}}}|
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#description|'''Description''']] 
{{!}} {{{description}}}
{{!}}-
}}
{{#if:{{{author|}}}{{{username|}}} |
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#username|'''Author(s)''']]
{{!}} {{#if: {{{username|}}} |&lt;!--
      --&gt;{{#ifeq: {{{username}}}|{{{author|{{{username}}}&lt;!-- --&gt;}}}|&lt;!--
         nothing
      --&gt;|&lt;!--else--&gt;&lt;!--
         --&gt;{{{author}}} (&lt;!--
      --&gt;}}&lt;!--
      --&gt;[[User:{{{username}}}|{{{username}}}]]&lt;!--
      --&gt;&lt;sup&gt;[[User talk:{{{username}}}|{{int:talkpagelinktext}}]]&lt;/sup&gt;&lt;!--
      --&gt;{{#ifeq: {{{username}}}|{{{author|{{{username}}}&lt;!-- --&gt;}}}|&lt;!--
         nothing
      --&gt;|&lt;!--else--&gt;&lt;!--
         --&gt;)&lt;!--
      --&gt;}}&lt;!--
   --&gt;|&lt;!--else--&gt;&lt;!--
      --&gt;{{{author}}}&lt;!--
   --&gt;}}
{{!}}-
}}
{{#if:{{{latest release version|{{{latest_release_version|{{{version|}}}}}}}}}|
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#version|'''Latest version''']]
{{!}} {{{latest release version|{{{latest_release_version|{{{version|}}}}}}}}}{{#if:{{{latest release date|{{{latest_release_date|{{{update|}}}}}}}}}|&amp;#160;({{{latest release date|{{{latest_release_date|{{{update}}})}}}}}}}}
{{!}}-
}}
{{#if:{{{latest preview version|{{{latest_peview_version|{{{version_preview|{{{version preview|}}}}}}}}}}}}|
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#version|'''Latest preview version''']]
{{!}} {{{latest preview version|{{{latest_preview_version|{{{version_preview|{{{version preview|}}}}}}}}}}}}{{#if:{{{latest preview version|{{{latest_preview_version|{{{update_preview|{{{update preview|}}}}}}}}}}}}|&amp;#160;({{{latest preview version|{{{latest_preview_version|{{{update_preview|{{{update preview}}}}}}}}}}}})}}
{{!}}-
}}
{{#if:{{{mediawiki|}}}|
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#mediawiki|'''MediaWiki''']]
{{!}} {{{mediawiki}}}
{{!}}-
}}
{{#if:{{{php|}}}|
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#php|'''PHP''']]
{{!}} {{{php}}}
{{!}}-
}}
{{#if:{{{needs-updatephp|}}}|
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#needs-updatephp|&lt;abbr title="'php update.php' needed after installation"&gt;'''Database&amp;nbsp;changes'''&lt;/abbr&gt;]]
{{!}} {{#switch:{{{needs-updatephp}}}|yes|Yes=Yes|no|No=No|{{{needs-updatephp}}}}}
{{!}}-
}}
{{#if:{{{composer|}}}|
{{!}} style="vertical-align: top" {{!}} [[Composer|&lt;abbr title="Supports 'Composer' for installation"&gt;'''Composer'''&lt;/abbr&gt;]]
{{!}} [https://packagist.org/packages/{{{composer}}} {{{composer}}}] {{#ifeq:{{{templatemode|}}}|nocats|&lt;!-- do nothing --&gt;|&lt;!--else--&gt;{{#if:{{{composer|}}}|[[Category:Extensions supporting Composer{{translation}}]]|}} }}
}}
{{!}}-
{{#if:{{{table1|}}}|
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#table1|'''Tables''']]
{{!}} [[{{FULLPAGENAME}}/{{{table1}}} table|{{{table1}}}]]&lt;!--
--&gt;{{#if:{{{table2|}}}|&lt;br /&gt;[[{{FULLPAGENAME}}/{{{table2}}} table|{{{table2}}}]]&lt;!-- --&gt;}}&lt;!--
--&gt;{{#if:{{{table3|}}}|&lt;br /&gt;[[{{FULLPAGENAME}}/{{{table3}}} table|{{{table3}}}]]&lt;!-- --&gt;}}&lt;!--
--&gt;{{#if:{{{table4|}}}|&lt;br /&gt;[[{{FULLPAGENAME}}/{{{table4}}} table|{{{table4}}}]]&lt;!-- --&gt;}}&lt;!--
--&gt;{{#if:{{{table5|}}}|&lt;br /&gt;[[{{FULLPAGENAME}}/{{{table5}}} table|{{{table5}}}]]&lt;!-- --&gt;}}&lt;!--
--&gt;{{#if:{{{table6|}}}|&lt;br /&gt;[[{{FULLPAGENAME}}/{{{table6}}} table|{{{table6}}}]]&lt;!-- --&gt;}}&lt;!--
--&gt;{{#if:{{{table7|}}}|&lt;br /&gt;[[{{FULLPAGENAME}}/{{{table7}}} table|{{{table7}}}]]&lt;!-- --&gt;}}&lt;!--
--&gt;{{#if:{{{table8|}}}|&lt;br /&gt;[[{{FULLPAGENAME}}/{{{table8}}} table|{{{table8}}}]]&lt;!-- --&gt;}}&lt;!--
--&gt;{{#if:{{{table9|}}}|&lt;br /&gt;[[{{FULLPAGENAME}}/{{{table9}}} table|{{{table9}}}]]&lt;!-- --&gt;}}&lt;!--
--&gt;{{#if:{{{table10|}}}|&lt;br /&gt;[[{{FULLPAGENAME}}/{{{table10}}} table|{{{table10}}}]]&lt;!-- --&gt;}}
{{!}}-
}}
|-
| style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#license|'''License''']]
| {{#if:{{{license|}}}|{{#invoke:Extension|getFormattedLicense|{{{license}}}}}|No license specified{{#if:{{{nocats|}}}||[[Category:Extensions with no license specified{{translation}}]]}}}}
|-
| style="vertical-align: top" | '''Download'''
| &lt;!--
--&gt;{{#if:{{{download|}}}|{{{download}}}|''No link''}}&lt;!--
--&gt;{{#if:{{{readme|}}}|&lt;br /&gt;{{{readme}}}&lt;!-- --&gt;}}&lt;!--
--&gt;{{#if:{{{changelog|}}}|&lt;br /&gt;{{{changelog}}}&lt;!-- --&gt;}}
|-
{{#if:{{{example|}}}|
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#example|'''Example''']]
{{!}} {{{example}}}
{{!}}-
}}
{{#if:{{{namespace|}}}|
{{!}} style="vertical-align: top" {{!}} [[Special:MyLanguage/Template:Extension#namespace|'''Namespace''']]
{{!}} {{{namespace|}}}
{{!}}-
}}
{{#if:{{{parameters|}}}|
{{!}} style="padding: 0pt;" colspan="2" {{!}}&lt;!--
   --&gt;
{{{!}} class="mw-collapsible mw-collapsed" style="border-collapse: collapse; width: 100%;"
{{!}}-
! style="vertical-align: top; text-align: left; padding: 0.2em 0.5em;" {{!}} [[Special:MyLanguage/Template:Extension#parameters|'''Parameters''']]
{{!}}-
{{!}}
{{{parameters}}}
{{!}}}
{{!}}-
}}
{{#if:{{{tags|}}}|
{{!}} style="padding: 0pt;" colspan="2" {{!}}
{{{!}} class="mw-collapsible mw-collapsed" style="border-collapse: collapse; width: 100%;"
{{!}}-
! style="vertical-align: top; text-align: left; padding: 0.2em 0.5em;" {{!}} [[Special:MyLanguage/Template:Extension#tags|'''Tags''']]
{{!}}-
{{!}} {{{tags}}}
{{!}}}
{{!}}-
}}
{{#if:{{{rights|}}}|
{{!}} style="padding: 0pt;" colspan="2" {{!}}
{{{!}} class="mw-collapsible mw-collapsed" style="border-collapse: collapse; width: 100%;"
{{!}}-
! style="vertical-align: top; text-align: left; padding: 0.2em 0.5em;" {{!}} [[Special:MyLanguage/Template:Extension#rights|'''Added rights''']]
{{!}}-
{{!}}
{{{rights}}}
{{#ifeq:{{{templatemode|}}}|nocats|&lt;!-- do nothing --&gt;|&lt;!--else--&gt;{{#if:{{{rights|}}}|[[Category:Extensions which add rights{{translation}}]]|}} }}
{{!}}}
{{!}}-
}}
{{#if:{{{hook1|}}}|
{{!}} style="padding: 0pt;" colspan="2" {{!}}
{{{!}} class="mw-collapsible mw-collapsed" style="border-collapse: collapse; width: 100%;"
{{!}}-
! style="vertical-align: top; text-align: left; padding: 0.2em 0.5em;" {{!}} [[Special:MyLanguage/Template:Extension#hook|'''Hooks used''']]
{{!}}-
{{!}}&lt;!--
      --&gt;{{#ifeq:{{{templatemode|}}}|nocats|&lt;!--
         --&gt;{{Foreach|Extension/HookInUseNoCats|delim=&lt;br/&gt;|&lt;!--
            --&gt;{{{hook1}}}|{{{hook2|}}}|{{{hook3|}}}|{{{hook4|}}}|{{{hook5|}}}|{{{hook6|}}}|&lt;!--
            --&gt;{{{hook7|}}}|{{{hook8|}}}|{{{hook9|}}}|{{{hook10|}}}|{{{hook11|}}}|{{{hook12|}}}|&lt;!--
            --&gt;{{{hook13|}}}|{{{hook14|}}}|{{{hook15|}}}|{{{hook16|}}}|{{{hook17|}}}|{{{hook18|}}}|&lt;!--
            --&gt;{{{hook19|}}}|{{{hook20|}}}|{{{hook21|}}}|{{{hook22|}}}|{{{hook23|}}}|{{{hook24|}}}|&lt;!--
            --&gt;{{{hook25|}}}|{{{hook26|}}}|{{{hook27|}}}|{{{hook28|}}}|{{{hook29|}}}|{{{hook30|}}}|&lt;!--
            --&gt;{{{hook31|}}}|{{{hook32|}}}|{{{hook33|}}}|{{{hook34|}}}|{{{hook35|}}}|{{{hook36|}}}|&lt;!--
            --&gt;{{{hook37|}}}|{{{hook38|}}}|{{{hook39|}}}|{{{hook40|}}}|{{{hook41|}}}|{{{hook42|}}}|&lt;!--
            --&gt;{{{hook43|}}}|{{{hook44|}}}|{{{hook45|}}}|{{{hook46|}}}|{{{hook47|}}}|{{{hook48|}}}&lt;!--
         --&gt;}}&lt;!--
      --&gt;|&lt;!--else--&gt;&lt;!--
         --&gt;{{Foreach|Extension/HookInUse|delim=&lt;br/&gt;|&lt;!--
            --&gt;{{{hook1}}}|{{{hook2|}}}|{{{hook3|}}}|{{{hook4|}}}|{{{hook5|}}}|{{{hook6|}}}|&lt;!--
            --&gt;{{{hook7|}}}|{{{hook8|}}}|{{{hook9|}}}|{{{hook10|}}}|{{{hook11|}}}|{{{hook12|}}}|&lt;!--
            --&gt;{{{hook13|}}}|{{{hook14|}}}|{{{hook15|}}}|{{{hook16|}}}|{{{hook17|}}}|{{{hook18|}}}|&lt;!--
            --&gt;{{{hook19|}}}|{{{hook20|}}}|{{{hook21|}}}|{{{hook22|}}}|{{{hook23|}}}|{{{hook24|}}}|&lt;!--
            --&gt;{{{hook25|}}}|{{{hook26|}}}|{{{hook27|}}}|{{{hook28|}}}|{{{hook29|}}}|{{{hook30|}}}|&lt;!--
            --&gt;{{{hook31|}}}|{{{hook32|}}}|{{{hook33|}}}|{{{hook34|}}}|{{{hook35|}}}|{{{hook36|}}}|&lt;!--
            --&gt;{{{hook37|}}}|{{{hook38|}}}|{{{hook39|}}}|{{{hook40|}}}|{{{hook41|}}}|{{{hook42|}}}|&lt;!--
            --&gt;{{{hook43|}}}|{{{hook44|}}}|{{{hook45|}}}|{{{hook46|}}}|{{{hook47|}}}|{{{hook48|}}}&lt;!--
         --&gt;}}&lt;!--
      --&gt;}}&lt;!--
   --&gt;
{{!}}}
{{!}}-
}}
{{#if:{{{newhook1|}}}|
{{!}} style="padding: 0pt;" colspan="2" {{!}}
{{{!}} class="mw-collapsible mw-collapsed" style="border-collapse: collapse; width: 100%;"
{{!}}-
! style="vertical-align: top; text-align: left; padding: 0.2em 0.5em;" {{!}} [[Special:MyLanguage/Template:Extension#newhook|'''Hooks provided''']]
{{!}}-
{{!}}&lt;!--
      --&gt;{{Foreach|Extension/HookProvided|delim=&lt;br/&gt;|&lt;!--
         --&gt;{{{newhook1}}}|{{{newhook2|}}}|{{{newhook3|}}}|{{{newhook4|}}}|{{{newhook5|}}}|{{{newhook6|}}}|&lt;!--
         --&gt;{{{newhook7|}}}|{{{newhook8|}}}|{{{newhook9|}}}|{{{newhook10|}}}|{{{newhook11|}}}|{{{newhook12|}}}|&lt;!--
         --&gt;{{{newhook13|}}}|{{{newhook14|}}}|{{{newhook15|}}}|{{{newhook16|}}}|{{{newhook17|}}}|{{{newhook18|}}}|&lt;!--
         --&gt;{{{newhook19|}}}|{{{newhook20|}}}|{{{newhook21|}}}|{{{newhook22|}}}|{{{newhook23|}}}|{{{newhook24|}}}|&lt;!--
         --&gt;{{{newhook25|}}}|{{{newhook26|}}}|{{{newhook27|}}}|{{{newhook28|}}}|{{{newhook29|}}}|{{{newhook30|}}}|&lt;!--
         --&gt;{{{newhook31|}}}|{{{newhook32|}}}|{{{newhook33|}}}|{{{newhook34|}}}|{{{newhook35|}}}|{{{newhook36|}}}|&lt;!--
         --&gt;{{{newhook37|}}}|{{{newhook38|}}}|{{{newhook39|}}}|{{{newhook40|}}}|{{{newhook41|}}}|{{{newhook42|}}}|&lt;!--
         --&gt;{{{newhook43|}}}|{{{newhook44|}}}|{{{newhook45|}}}|{{{newhook46|}}}|{{{newhook47|}}}|{{{newhook48|}}}&lt;!--
      --&gt;}}&lt;!--
   --&gt;
{{!}}}
{{!}}-
}}
{{#if:{{{compatibility|}}}|
{{!}} colspan="2" {{!}}
{{{compatibility}}}
{{!}}-
}}
{{!}} colspan="2" style="text-align:center;" {{!}}
[[translatewiki:Special:Translate/{{{translate|ext-{{lc:{{#invoke:String/enwiki|replace|{{BASEPAGENAME}}| |}}}}}}}|Translate the {{BASEPAGENAME}} extension]] if it is available at translatewiki.net
{{!}}-
{{!}} colspan="2" style="text-align:center;" {{!}}&lt;!--
Note: this next check suppresses the 'Check usage' link if page is: a subpage, not in Extension: namespace, or if suppressed by 'templatemode=nocats' or 'nousage=true'.
--&gt;{{#if:{{{nousage|{{#ifeq:{{{templatemode|}}}|nocats
                      |no usage
                      |{{#ifeq:{{NAMESPACE}}|{{ns:102}}
                         |
                         |no usage
                       }}
                      {{#ifeq:{{{templatemode|}}}|nousage
                         |no usage
                       }}
                    }}}}}
     |&lt;!-- no usage --&gt;|
Check [[wikiapiary:Extension:{{{CheckUsageNameOverride|{{BASEPAGENAMEE}}}}}|usage&amp;nbsp;and&amp;nbsp;version&amp;nbsp;matrix]]; [https://git.wikimedia.org/metrics/mediawiki%2Fextensions%2F{{{CheckUsageNameOverride|{{BASEPAGENAMEE}}}}} code&amp;nbsp;metrics]&lt;!--
--&gt;}}
{{#if:{{{vagrant-role|}}} |
{{!}}-
{{!}} style="vertical-align: top; text-align: left; padding: 0.2em 0.5em;" {{!}} [[MediaWiki-Vagrant#Using_roles{{!}}'''Vagrant role''']]
{{!}} [https://doc.wikimedia.org/mediawiki-vagrant/classes/role/{{{vagrant-role}}}.html {{{vagrant-role}}}]
}}
{{!}}-
{{#if: {{{phabricator|{{{bugzilla|}}}}}} |
{{!}} style="vertical-align: top" {{!}} 
'''[[Phabricator|Issues]]:''' 
{{!}}[[phab:tag/{{lc:{{{phabricator|MediaWiki-extensions-{{{bugzilla}}}}}}}}|Open tasks]] · [https://phabricator.wikimedia.org/maniphest/task/create/?projects={{{phabricator|MediaWiki-extensions-{{{bugzilla}}}}}} Report a bug]
{{!}}-
}}
|}&lt;!--
--&gt;{{#ifeq:{{{templatemode|}}}|nocats|&lt;!--
   nothing--&gt;&lt;!--
--&gt;|&lt;!--else--&gt;&lt;!--
   --&gt;{{DEFAULTSORT:{{#if:{{{name|}}}|&lt;!--
      --&gt;{{uc:{{{name}}}&lt;!-- --&gt;}}&lt;!--
   --&gt;|&lt;!--else--&gt;&lt;!--
      --&gt;{{uc:{{PAGENAME}}&lt;!-- --&gt;}}&lt;!--
   --&gt;}}&lt;!-- --&gt;}}&lt;!--
   --&gt;[[Category:All extensions{{translation}}]]&lt;!--
--&gt;}}&lt;/includeonly&gt;&lt;noinclude&gt;{{ {{TNTN|Documentation}} }}
[[Category:Info templates{{translation}}|{{PAGENAME}}]]
[[Category:Extension creation{{translation}}]]
[[Category:Categorizing templates{{translation}}|{{PAGENAME}}]]
[[Category:Extension templates{{translation}}]]
{{languages|Template:Extension}}
&lt;/noinclude&gt;</text>
    <sha1>014b01e5b79ade1561902db5dc5c7e8f1adcc071</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:TNTN</title>
  <ns>10</ns>
  <id>81</id>
  <revision>
    <id>219</id>
    <timestamp>2016-01-06T06:11:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Redirected page to [[Template:Translatable template name]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="49" xml:space="preserve">#REDIRECT [[Template:Translatable template name]]</text>
    <sha1>51aba18c9e7edde0de5272258792895d16b983c2</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Module:Documentation</title>
  <ns>0</ns>
  <id>83</id>
  <revision>
    <id>221</id>
    <timestamp>2016-01-06T06:14:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "-- This module implements {{documentation}}.  -- Get required modules. local getArgs = require('Module:Arguments').getArgs local messageBox = require('Module:Message box')  --..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="36249" xml:space="preserve">-- This module implements {{documentation}}.

-- Get required modules.
local getArgs = require('Module:Arguments').getArgs
local messageBox = require('Module:Message box')

-- Get the config table.
local cfg = mw.loadData('Module:Documentation/config')

local p = {}

-- Often-used functions.
local ugsub = mw.ustring.gsub

----------------------------------------------------------------------------
-- Helper functions
--
-- These are defined as local functions, but are made available in the p
-- table for testing purposes.
----------------------------------------------------------------------------

local function message(cfgKey, valArray, expectType)
	--[[
	-- Gets a message from the cfg table and formats it if appropriate.
	-- The function raises an error if the value from the cfg table is not
	-- of the type expectType. The default type for expectType is 'string'.
	-- If the table valArray is present, strings such as $1, $2 etc. in the
	-- message are substituted with values from the table keys [1], [2] etc.
	-- For example, if the message "foo-message" had the value 'Foo $2 bar $1.',
	-- message('foo-message', {'baz', 'qux'}) would return "Foo qux bar baz."
	--]]
	local msg = cfg[cfgKey]
	expectType = expectType or 'string'
	if type(msg) ~= expectType then
		error('message: type error in message cfg.' .. cfgKey .. ' (' .. expectType .. ' expected, got ' .. type(msg) .. ')', 2)
	end
	if not valArray then
		return msg
	end

	local function getMessageVal(match)
		match = tonumber(match)
		return valArray[match] or error('message: no value found for key $' .. match .. ' in message cfg.' .. cfgKey, 4)
	end

	local ret = ugsub(msg, '$([1-9][0-9]*)', getMessageVal)
	return ret
end

p.message = message

local function makeWikilink(page, display)
	if display then
		return mw.ustring.format('[[%s|%s]]', page, display)
	else
		return mw.ustring.format('[[%s]]', page)
	end
end

p.makeWikilink = makeWikilink

local function makeCategoryLink(cat, sort)
	local catns = mw.site.namespaces[14].name
	return makeWikilink(catns .. ':' .. cat, sort)
end

p.makeCategoryLink = makeCategoryLink

local function makeUrlLink(url, display)
	return mw.ustring.format('[%s %s]', url, display)
end

p.makeUrlLink = makeUrlLink

local function makeToolbar(...)
	local ret = {}
	local lim = select('#', ...)
	if lim &lt; 1 then
		return nil
	end
	for i = 1, lim do
		ret[#ret + 1] = select(i, ...)
	end
	return '&lt;small style="font-style: normal;"&gt;(' .. table.concat(ret, ' &amp;#124; ') .. ')&lt;/small&gt;'
end	

p.makeToolbar = makeToolbar

----------------------------------------------------------------------------
-- Argument processing
----------------------------------------------------------------------------

local function makeInvokeFunc(funcName)
	return function (frame)
		local args = getArgs(frame, {
			valueFunc = function (key, value)
				if type(value) == 'string' then
					value = value:match('^%s*(.-)%s*$') -- Remove whitespace.
					if key == 'heading' or value ~= '' then
						return value
					else
						return nil
					end
				else
					return value
				end
			end
		})
		return p[funcName](args)
	end
end

----------------------------------------------------------------------------
-- Main function
----------------------------------------------------------------------------

p.main = makeInvokeFunc('_main')

function p._main(args)
	--[[
	-- This function defines logic flow for the module.
	-- @args - table of arguments passed by the user
	-- 
	-- Messages:
	-- 'main-div-id' --&gt; 'template-documentation'
	-- 'main-div-classes' --&gt; 'template-documentation iezoomfix'
	--]]
	local env = p.getEnvironment(args)
	local root = mw.html.create()
	root
		:wikitext(p.protectionTemplate(env))
		:wikitext(p.sandboxNotice(args, env))
		 -- This div tag is from {{documentation/start box}}, but moving it here
		 -- so that we don't have to worry about unclosed tags.
		:tag('div')
			:attr('id', message('main-div-id'))
			:addClass(message('main-div-classes'))
			:css('padding', '12px')
			:newline()
			:wikitext(p._startBox(args, env))
			:wikitext(p._content(args, env))
			:tag('div')
				:css('clear', 'both') -- So right or left floating items don't stick out of the doc box.
				:newline()
				:done()
			:done()
		:wikitext(p._endBox(args, env))
		:wikitext(p.addTrackingCategories(env))
	return tostring(root)
end

----------------------------------------------------------------------------
-- Environment settings
----------------------------------------------------------------------------

function p.getEnvironment(args)
	--[[
	-- Returns a table with information about the environment, including title objects and other namespace- or
	-- path-related data.
	-- @args - table of arguments passed by the user
	--
	-- Title objects include:
	-- env.title - the page we are making documentation for (usually the current title)
	-- env.templateTitle - the template (or module, file, etc.)
	-- env.docTitle - the /doc subpage.
	-- env.sandboxTitle - the /sandbox subpage.
	-- env.testcasesTitle - the /testcases subpage.
	-- env.printTitle - the print version of the template, located at the /Print subpage.
	--
	-- Data includes:
	-- env.protectionLevels - the protection levels table of the title object.
	-- env.subjectSpace - the number of the title's subject namespace.
	-- env.docSpace - the number of the namespace the title puts its documentation in.
	-- env.docpageBase - the text of the base page of the /doc, /sandbox and /testcases pages, with namespace.
	-- env.compareUrl - URL of the Special:ComparePages page comparing the sandbox with the template.
	-- 
	-- All table lookups are passed through pcall so that errors are caught. If an error occurs, the value
	-- returned will be nil.
	--]]
	
	local env, envFuncs = {}, {}

	-- Set up the metatable. If triggered we call the corresponding function in the envFuncs table. The value
	-- returned by that function is memoized in the env table so that we don't call any of the functions
	-- more than once. (Nils won't be memoized.)
	setmetatable(env, {
		__index = function (t, key)
			local envFunc = envFuncs[key]
			if envFunc then
				local success, val = pcall(envFunc)
				if success then
					env[key] = val -- Memoise the value.
					return val
				end
			end
			return nil
		end
	})	

	function envFuncs.title()
		-- The title object for the current page, or a test page passed with args.page.
		local title
		local titleArg = args.page
		if titleArg then
			title = mw.title.new(titleArg)
		else
			title = mw.title.getCurrentTitle()
		end
		return title
	end

	function envFuncs.templateTitle()
		--[[
		-- The template (or module, etc.) title object.
		-- Messages:
		-- 'sandbox-subpage' --&gt; 'sandbox'
		-- 'testcases-subpage' --&gt; 'testcases'
		--]]
		local subjectSpace = env.subjectSpace
		local title = env.title
		local subpage = title.subpageText
		if subpage == message('sandbox-subpage') or subpage == message('testcases-subpage') then
			return mw.title.makeTitle(subjectSpace, title.baseText)
		else
			return mw.title.makeTitle(subjectSpace, title.text)
		end
	end

	function envFuncs.docTitle()
		--[[
		-- Title object of the /doc subpage.
		-- Messages:
		-- 'doc-subpage' --&gt; 'doc'
		--]]
		local title = env.title
		local docname = args[1] -- User-specified doc page.
		local docpage
		if docname then
			docpage = docname
		else
			docpage = env.docpageBase .. '/' .. message('doc-subpage')
		end
		return mw.title.new(docpage)
	end
	
	function envFuncs.sandboxTitle()
		--[[
		-- Title object for the /sandbox subpage.
		-- Messages:
		-- 'sandbox-subpage' --&gt; 'sandbox'
		--]]
		return mw.title.new(env.docpageBase .. '/' .. message('sandbox-subpage'))
	end
	
	function envFuncs.testcasesTitle()
		--[[
		-- Title object for the /testcases subpage.
		-- Messages:
		-- 'testcases-subpage' --&gt; 'testcases'
		--]]
		return mw.title.new(env.docpageBase .. '/' .. message('testcases-subpage'))
	end
	
	function envFuncs.printTitle()
		--[[
		-- Title object for the /Print subpage.
		-- Messages:
		-- 'print-subpage' --&gt; 'Print'
		--]]
		return env.templateTitle:subPageTitle(message('print-subpage'))
	end

	function envFuncs.protectionLevels()
		-- The protection levels table of the title object.
		return env.title.protectionLevels
	end

	function envFuncs.subjectSpace()
		-- The subject namespace number.
		return mw.site.namespaces[env.title.namespace].subject.id
	end

	function envFuncs.docSpace()
		-- The documentation namespace number. For most namespaces this is the same as the
		-- subject namespace. However, pages in the Article, File, MediaWiki or Category
		-- namespaces must have their /doc, /sandbox and /testcases pages in talk space.
		local subjectSpace = env.subjectSpace
		if subjectSpace == 0 or subjectSpace == 6 or subjectSpace == 8 or subjectSpace == 14 then
			return subjectSpace + 1
		else
			return subjectSpace
		end
	end

	function envFuncs.docpageBase()
		-- The base page of the /doc, /sandbox, and /testcases subpages.
		-- For some namespaces this is the talk page, rather than the template page.
		local templateTitle = env.templateTitle
		local docSpace = env.docSpace
		local docSpaceText = mw.site.namespaces[docSpace].name
		-- Assemble the link. docSpace is never the main namespace, so we can hardcode the colon.
		return docSpaceText .. ':' .. templateTitle.text
	end
	
	function envFuncs.compareUrl()
		-- Diff link between the sandbox and the main template using [[Special:ComparePages]].
		local templateTitle = env.templateTitle
		local sandboxTitle = env.sandboxTitle
		if templateTitle.exists and sandboxTitle.exists then
			local compareUrl = mw.uri.fullUrl(
				'Special:ComparePages',
				{page1 = templateTitle.prefixedText, page2 = sandboxTitle.prefixedText}
			)
			return tostring(compareUrl)
		else
			return nil
		end
	end		

	return env
end	

----------------------------------------------------------------------------
-- Auxiliary templates
----------------------------------------------------------------------------

function p.sandboxNotice(args, env)
	--[=[
	-- Generates a sandbox notice for display above sandbox pages.
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	-- 
	-- Messages:
	-- 'sandbox-notice-image' --&gt; '[[Image:Sandbox.svg|50px|alt=|link=]]'
	-- 'sandbox-notice-blurb' --&gt; 'This is the $1 for $2.'
	-- 'sandbox-notice-diff-blurb' --&gt; 'This is the $1 for $2 ($3).'
	-- 'sandbox-notice-pagetype-template' --&gt; '[[Wikipedia:Template test cases|template sandbox]] page'
	-- 'sandbox-notice-pagetype-module' --&gt; '[[Wikipedia:Template test cases|module sandbox]] page'
	-- 'sandbox-notice-pagetype-other' --&gt; 'sandbox page'
	-- 'sandbox-notice-compare-link-display' --&gt; 'diff'
	-- 'sandbox-notice-testcases-blurb' --&gt; 'See also the companion subpage for $1.'
	-- 'sandbox-notice-testcases-link-display' --&gt; 'test cases'
	-- 'sandbox-category' --&gt; 'Template sandboxes'
	--]=]
	local title = env.title
	local sandboxTitle = env.sandboxTitle
	local templateTitle = env.templateTitle
	local subjectSpace = env.subjectSpace
	if not (subjectSpace and title and sandboxTitle and templateTitle and mw.title.equals(title, sandboxTitle)) then
		return nil
	end
	-- Build the table of arguments to pass to {{ombox}}. We need just two fields, "image" and "text".
	local omargs = {}
	omargs.image = message('sandbox-notice-image')
	-- Get the text. We start with the opening blurb, which is something like
	-- "This is the template sandbox for [[Template:Foo]] (diff)."
	local text = ''
	local frame = mw.getCurrentFrame()
	local isPreviewing = frame:preprocess('{{REVISIONID}}') == '' -- True if the page is being previewed.
	local pagetype
	if subjectSpace == 10 then
		pagetype = message('sandbox-notice-pagetype-template')
	elseif subjectSpace == 828 then
		pagetype = message('sandbox-notice-pagetype-module')
	else
		pagetype = message('sandbox-notice-pagetype-other')
	end
	local templateLink = makeWikilink(templateTitle.prefixedText)
	local compareUrl = env.compareUrl
	if isPreviewing or not compareUrl then
		text = text .. message('sandbox-notice-blurb', {pagetype, templateLink})
	else
		local compareDisplay = message('sandbox-notice-compare-link-display')
		local compareLink = makeUrlLink(compareUrl, compareDisplay)
		text = text .. message('sandbox-notice-diff-blurb', {pagetype, templateLink, compareLink})
	end
	-- Get the test cases page blurb if the page exists. This is something like
	-- "See also the companion subpage for [[Template:Foo/testcases|test cases]]."
	local testcasesTitle = env.testcasesTitle
	if testcasesTitle and testcasesTitle.exists then
		if testcasesTitle.namespace == mw.site.namespaces.Module.id then
			local testcasesLinkDisplay = message('sandbox-notice-testcases-link-display')
			local testcasesRunLinkDisplay = message('sandbox-notice-testcases-run-link-display')
			local testcasesLink = makeWikilink(testcasesTitle.prefixedText, testcasesLinkDisplay)
			local testcasesRunLink = makeWikilink(testcasesTitle.talkPageTitle.prefixedText, testcasesRunLinkDisplay)
			text = text .. '&lt;br /&gt;' .. message('sandbox-notice-testcases-run-blurb', {testcasesLink, testcasesRunLink})
		else
			local testcasesLinkDisplay = message('sandbox-notice-testcases-link-display')
			local testcasesLink = makeWikilink(testcasesTitle.prefixedText, testcasesLinkDisplay)
			text = text .. '&lt;br /&gt;' .. message('sandbox-notice-testcases-blurb', {testcasesLink})
		end
	end
	-- Add the sandbox to the sandbox category.
	text = text .. makeCategoryLink(message('sandbox-category'))
	omargs.text = text
	local ret = '&lt;div style="clear: both;"&gt;&lt;/div&gt;'
	ret = ret .. messageBox.main('ombox', omargs)
	return ret
end

function p.protectionTemplate(env)
	-- Generates the padlock icon in the top right.
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	-- Messages:
	-- 'protection-template' --&gt; 'pp-template'
	-- 'protection-template-args' --&gt; {docusage = 'yes'}
	local title = env.title
	local protectionLevels
	local protectionTemplate = message('protection-template')
	local namespace = title.namespace
	if not (protectionTemplate and (namespace == 10 or namespace == 828)) then
		-- Don't display the protection template if we are not in the template or module namespaces.
		return nil
	end
	protectionLevels = env.protectionLevels
	if not protectionLevels then
		return nil
	end
	local editLevels = protectionLevels.edit
	local moveLevels = protectionLevels.move
	if moveLevels and moveLevels[1] == 'sysop' or editLevels and editLevels[1] then
		-- The page is full-move protected, or full, template, or semi-protected.
		local frame = mw.getCurrentFrame()
		return frame:expandTemplate{title = protectionTemplate, args = message('protection-template-args', nil, 'table')}
	else
		return nil
	end
end

----------------------------------------------------------------------------
-- Start box
----------------------------------------------------------------------------

p.startBox = makeInvokeFunc('_startBox')

function p._startBox(args, env)
	--[[
	-- This function generates the start box.
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	-- 
	-- The actual work is done by p.makeStartBoxLinksData and p.renderStartBoxLinks which make
	-- the [view] [edit] [history] [purge] links, and by p.makeStartBoxData and p.renderStartBox
	-- which generate the box HTML.
	--]]
	env = env or p.getEnvironment(args)
	local links
	local content = args.content
	if not content then
		-- No need to include the links if the documentation is on the template page itself.
		local linksData = p.makeStartBoxLinksData(args, env)
		if linksData then
			links = p.renderStartBoxLinks(linksData)
		end
	end
	-- Generate the start box html.
	local data = p.makeStartBoxData(args, env, links)
	if data then
		return p.renderStartBox(data)
	else
		-- User specified no heading.
		return nil
	end
end

function p.makeStartBoxLinksData(args, env)
	--[[
	-- Does initial processing of data to make the [view] [edit] [history] [purge] links.
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	-- 
	-- Messages:
	-- 'view-link-display' --&gt; 'view'
	-- 'edit-link-display' --&gt; 'edit'
	-- 'history-link-display' --&gt; 'history'
	-- 'purge-link-display' --&gt; 'purge'
	-- 'file-docpage-preload' --&gt; 'Template:Documentation/preload-filespace'
	-- 'module-preload' --&gt; 'Template:Documentation/preload-module-doc'
	-- 'docpage-preload' --&gt; 'Template:Documentation/preload'
	-- 'create-link-display' --&gt; 'create'
	--]]
	local subjectSpace = env.subjectSpace
	local title = env.title
	local docTitle = env.docTitle
	if not title or not docTitle then
		return nil
	end

	local data = {}
	data.title = title
	data.docTitle = docTitle
	-- View, display, edit, and purge links if /doc exists.
	data.viewLinkDisplay = message('view-link-display')
	data.editLinkDisplay = message('edit-link-display')
	data.historyLinkDisplay = message('history-link-display')
	data.purgeLinkDisplay = message('purge-link-display')
	-- Create link if /doc doesn't exist.
	local preload = args.preload
	if not preload then
		if subjectSpace == 6 then -- File namespace
			preload = message('file-docpage-preload')
		elseif subjectSpace == 828 then -- Module namespace
			preload = message('module-preload')
		else
			preload = message('docpage-preload')
		end
	end
	data.preload = preload
	data.createLinkDisplay = message('create-link-display')
	return data
end

function p.renderStartBoxLinks(data)
	--[[
	-- Generates the [view][edit][history][purge] or [create] links from the data table.
	-- @data - a table of data generated by p.makeStartBoxLinksData
	--]]
	
	local function escapeBrackets(s)
		-- Escapes square brackets with HTML entities.
		s = s:gsub('%[', '&amp;#91;') -- Replace square brackets with HTML entities.
		s = s:gsub('%]', '&amp;#93;')
		return s
	end

	local ret
	local docTitle = data.docTitle
	local title = data.title
	if docTitle.exists then
		local viewLink = makeWikilink(docTitle.prefixedText, data.viewLinkDisplay)
		local editLink = makeUrlLink(docTitle:fullUrl{action = 'edit'}, data.editLinkDisplay)
		local historyLink = makeUrlLink(docTitle:fullUrl{action = 'history'}, data.historyLinkDisplay)
		local purgeLink = makeUrlLink(title:fullUrl{action = 'purge'}, data.purgeLinkDisplay)
		ret = '[%s] [%s] [%s] [%s]'
		ret = escapeBrackets(ret)
		ret = mw.ustring.format(ret, viewLink, editLink, historyLink, purgeLink)
	else
		local createLink = makeUrlLink(docTitle:fullUrl{action = 'edit', preload = data.preload}, data.createLinkDisplay)
		ret = '[%s]'
		ret = escapeBrackets(ret)
		ret = mw.ustring.format(ret, createLink)
	end
	return ret
end

function p.makeStartBoxData(args, env, links)
	--[=[
	-- Does initial processing of data to pass to the start-box render function, p.renderStartBox.
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	-- @links - a string containing the [view][edit][history][purge] links - could be nil if there's an error.
	--
	-- Messages:
	-- 'documentation-icon-wikitext' --&gt; '[[File:Test Template Info-Icon - Version (2).svg|50px|link=|alt=Documentation icon]]'
	-- 'template-namespace-heading' --&gt; 'Template documentation'
	-- 'module-namespace-heading' --&gt; 'Module documentation'
	-- 'file-namespace-heading' --&gt; 'Summary'
	-- 'other-namespaces-heading' --&gt; 'Documentation'
	-- 'start-box-linkclasses' --&gt; 'mw-editsection-like plainlinks'
	-- 'start-box-link-id' --&gt; 'doc_editlinks'
	-- 'testcases-create-link-display' --&gt; 'create'
	--]=]
	local subjectSpace = env.subjectSpace
	if not subjectSpace then
		-- Default to an "other namespaces" namespace, so that we get at least some output
		-- if an error occurs.
		subjectSpace = 2
	end
	local data = {}
	
	-- Heading
	local heading = args.heading -- Blank values are not removed.
	if heading == '' then
		-- Don't display the start box if the heading arg is defined but blank.
		return nil
	end
	if heading then
		data.heading = heading
	elseif subjectSpace == 10 then -- Template namespace
		data.heading = message('documentation-icon-wikitext') .. ' ' .. message('template-namespace-heading')
	elseif subjectSpace == 828 then -- Module namespace
		data.heading = message('documentation-icon-wikitext') .. ' ' .. message('module-namespace-heading')
	elseif subjectSpace == 6 then -- File namespace
		data.heading = message('file-namespace-heading')
	else
		data.heading = message('other-namespaces-heading')
	end
	
	-- Heading CSS
	local headingStyle = args['heading-style']
	if headingStyle then
		data.headingStyleText = headingStyle
	elseif subjectSpace == 10 then
		-- We are in the template or template talk namespaces.
		data.headingFontWeight = 'bold'
		data.headingFontSize = '125%'
	else
		data.headingFontSize = '150%'
	end
	
	-- Data for the [view][edit][history][purge] or [create] links.
	if links then
		data.linksClass = message('start-box-linkclasses')
		data.linksId = message('start-box-link-id')
		data.links = links
	end
	
	return data
end

function p.renderStartBox(data)
	-- Renders the start box html.
	-- @data - a table of data generated by p.makeStartBoxData.
	local sbox = mw.html.create('div')
	sbox
		:css('padding-bottom', '3px')
		:css('border-bottom', '1px solid #aaa')
		:css('margin-bottom', '1ex')
		:newline()
		:tag('span')
			:cssText(data.headingStyleText)
			:css('font-weight', data.headingFontWeight)
			:css('font-size', data.headingFontSize)
			:wikitext(data.heading)
	local links = data.links
	if links then
		sbox:tag('span')
			:addClass(data.linksClass)
			:attr('id', data.linksId)
			:wikitext(links)
	end
	return tostring(sbox)
end

----------------------------------------------------------------------------
-- Documentation content
----------------------------------------------------------------------------

p.content = makeInvokeFunc('_content')

function p._content(args, env)
	-- Displays the documentation contents
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	env = env or p.getEnvironment(args)
	local docTitle = env.docTitle
	local content = args.content
	if not content and docTitle and docTitle.exists then
		content = args._content or mw.getCurrentFrame():expandTemplate{title = docTitle.prefixedText}
	end
	-- The line breaks below are necessary so that "=== Headings ===" at the start and end
	-- of docs are interpreted correctly.
	return '\n' .. (content or '') .. '\n' 
end

p.contentTitle = makeInvokeFunc('_contentTitle')

function p._contentTitle(args, env)
	env = env or p.getEnvironment(args)
	local docTitle = env.docTitle
	if not args.content and docTitle and docTitle.exists then
		return docTitle.prefixedText
	else
		return ''
	end
end

----------------------------------------------------------------------------
-- End box
----------------------------------------------------------------------------

p.endBox = makeInvokeFunc('_endBox')

function p._endBox(args, env)
	--[=[
	-- This function generates the end box (also known as the link box).
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	-- 
	-- Messages:
	-- 'fmbox-id' --&gt; 'documentation-meta-data'
	-- 'fmbox-style' --&gt; 'background-color: #ecfcf4'
	-- 'fmbox-textstyle' --&gt; 'font-style: italic'
	-- 
	-- The HTML is generated by the {{fmbox}} template, courtesy of [[Module:Message box]].
	--]=]
	
	-- Get environment data.
	env = env or p.getEnvironment(args)
	local subjectSpace = env.subjectSpace
	local docTitle = env.docTitle
	if not subjectSpace or not docTitle then
		return nil
	end
		
	-- Check whether we should output the end box at all. Add the end
	-- box by default if the documentation exists or if we are in the
	-- user, module or template namespaces.
	local linkBox = args['link box']
	if linkBox == 'off'
		or not (
			docTitle.exists
			or subjectSpace == 2
			or subjectSpace == 828
			or subjectSpace == 10
		)
	then
		return nil
	end

	-- Assemble the arguments for {{fmbox}}.
	local fmargs = {}
	fmargs.id = message('fmbox-id') -- Sets 'documentation-meta-data'
	fmargs.image = 'none'
	fmargs.style = message('fmbox-style') -- Sets 'background-color: #ecfcf4'
	fmargs.textstyle = message('fmbox-textstyle') -- 'font-style: italic;'

	-- Assemble the fmbox text field.
	local text = ''
	if linkBox then
		text = text .. linkBox
	else
		text = text .. (p.makeDocPageBlurb(args, env) or '') -- "This documentation is transcluded from [[Foo]]." 
		if subjectSpace == 2 or subjectSpace == 10 or subjectSpace == 828 then
			-- We are in the user, template or module namespaces.
			-- Add sandbox and testcases links.
			-- "Editors can experiment in this template's sandbox and testcases pages."
			text = text .. (p.makeExperimentBlurb(args, env) or '')
			text = text .. '&lt;br /&gt;'
			if not args.content and not args[1] then
				-- "Please add categories to the /doc subpage."
				-- Don't show this message with inline docs or with an explicitly specified doc page,
				-- as then it is unclear where to add the categories.
				text = text .. (p.makeCategoriesBlurb(args, env) or '')
			end
			text = text .. ' ' .. (p.makeSubpagesBlurb(args, env) or '') --"Subpages of this template"
			local printBlurb = p.makePrintBlurb(args, env) -- Two-line blurb about print versions of templates.
			if printBlurb then
				text = text .. '&lt;br /&gt;' .. printBlurb
			end
		end
	end
	fmargs.text = text

	return messageBox.main('fmbox', fmargs)
end

function p.makeDocPageBlurb(args, env)
	--[=[
	-- Makes the blurb "This documentation is transcluded from [[Template:Foo]] (edit, history)".
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	-- 
	-- Messages:
	-- 'edit-link-display' --&gt; 'edit'
	-- 'history-link-display' --&gt; 'history'
	-- 'transcluded-from-blurb' --&gt; 
	-- 'The above [[Wikipedia:Template documentation|documentation]] 
	-- is [[Wikipedia:Transclusion|transcluded]] from $1.'
	-- 'module-preload' --&gt; 'Template:Documentation/preload-module-doc'
	-- 'create-link-display' --&gt; 'create'
	-- 'create-module-doc-blurb' --&gt;
	-- 'You might want to $1 a documentation page for this [[Wikipedia:Lua|Scribunto module]].'
	--]=]
	local docTitle = env.docTitle
	if not docTitle then
		return nil
	end
	local ret
	if docTitle.exists then
		-- /doc exists; link to it.
		local docLink = makeWikilink(docTitle.prefixedText)
		local editUrl = docTitle:fullUrl{action = 'edit'}
		local editDisplay = message('edit-link-display')
		local editLink = makeUrlLink(editUrl, editDisplay)
		local historyUrl = docTitle:fullUrl{action = 'history'}
		local historyDisplay = message('history-link-display')
		local historyLink = makeUrlLink(historyUrl, historyDisplay)
		ret = message('transcluded-from-blurb', {docLink})
			.. ' '
			.. makeToolbar(editLink, historyLink)
			.. '&lt;br /&gt;'
	elseif env.subjectSpace == 828 then
		-- /doc does not exist; ask to create it.
		local createUrl = docTitle:fullUrl{action = 'edit', preload = message('module-preload')}
		local createDisplay = message('create-link-display')
		local createLink = makeUrlLink(createUrl, createDisplay)
		ret = message('create-module-doc-blurb', {createLink})
			.. '&lt;br /&gt;'
	end
	return ret
end

function p.makeExperimentBlurb(args, env)
	--[[
	-- Renders the text "Editors can experiment in this template's sandbox (edit | diff) and testcases (edit) pages."
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	-- 
	-- Messages:
	-- 'sandbox-link-display' --&gt; 'sandbox'
	-- 'sandbox-edit-link-display' --&gt; 'edit'
	-- 'compare-link-display' --&gt; 'diff'
	-- 'module-sandbox-preload' --&gt; 'Template:Documentation/preload-module-sandbox'
	-- 'template-sandbox-preload' --&gt; 'Template:Documentation/preload-sandbox'
	-- 'sandbox-create-link-display' --&gt; 'create'
	-- 'mirror-edit-summary' --&gt; 'Create sandbox version of $1'
	-- 'mirror-link-display' --&gt; 'mirror'
	-- 'mirror-link-preload' --&gt; 'Template:Documentation/mirror'
	-- 'sandbox-link-display' --&gt; 'sandbox'
	-- 'testcases-link-display' --&gt; 'testcases'
	-- 'testcases-edit-link-display'--&gt; 'edit'
	-- 'template-sandbox-preload' --&gt; 'Template:Documentation/preload-sandbox'
	-- 'testcases-create-link-display' --&gt; 'create'
	-- 'testcases-link-display' --&gt; 'testcases'
	-- 'testcases-edit-link-display' --&gt; 'edit'
	-- 'module-testcases-preload' --&gt; 'Template:Documentation/preload-module-testcases'
	-- 'template-testcases-preload' --&gt; 'Template:Documentation/preload-testcases'
	-- 'experiment-blurb-module' --&gt; 'Editors can experiment in this module's $1 and $2 pages.'
	-- 'experiment-blurb-template' --&gt; 'Editors can experiment in this template's $1 and $2 pages.'
	--]]
	local subjectSpace = env.subjectSpace
	local templateTitle = env.templateTitle
	local sandboxTitle = env.sandboxTitle
	local testcasesTitle = env.testcasesTitle
	local templatePage = templateTitle.prefixedText
	if not subjectSpace or not templateTitle or not sandboxTitle or not testcasesTitle then
		return nil
	end
	-- Make links.
	local sandboxLinks, testcasesLinks
	if sandboxTitle.exists then
		local sandboxPage = sandboxTitle.prefixedText
		local sandboxDisplay = message('sandbox-link-display')
		local sandboxLink = makeWikilink(sandboxPage, sandboxDisplay)
		local sandboxEditUrl = sandboxTitle:fullUrl{action = 'edit'}
		local sandboxEditDisplay = message('sandbox-edit-link-display')
		local sandboxEditLink = makeUrlLink(sandboxEditUrl, sandboxEditDisplay)
		local compareUrl = env.compareUrl
		local compareLink
		if compareUrl then
			local compareDisplay = message('compare-link-display')
			compareLink = makeUrlLink(compareUrl, compareDisplay)
		end
		sandboxLinks = sandboxLink .. ' ' .. makeToolbar(sandboxEditLink, compareLink)
	else
		local sandboxPreload
		if subjectSpace == 828 then
			sandboxPreload = message('module-sandbox-preload')
		else
			sandboxPreload = message('template-sandbox-preload')
		end
		local sandboxCreateUrl = sandboxTitle:fullUrl{action = 'edit', preload = sandboxPreload}
		local sandboxCreateDisplay = message('sandbox-create-link-display')
		local sandboxCreateLink = makeUrlLink(sandboxCreateUrl, sandboxCreateDisplay)
		local mirrorSummary = message('mirror-edit-summary', {makeWikilink(templatePage)})
		local mirrorPreload = message('mirror-link-preload')
		local mirrorUrl = sandboxTitle:fullUrl{action = 'edit', preload = mirrorPreload, summary = mirrorSummary}
		local mirrorDisplay = message('mirror-link-display')
		local mirrorLink = makeUrlLink(mirrorUrl, mirrorDisplay)
		sandboxLinks = message('sandbox-link-display') .. ' ' .. makeToolbar(sandboxCreateLink, mirrorLink)
	end
	if testcasesTitle.exists then
		local testcasesPage = testcasesTitle.prefixedText
		local testcasesDisplay = message('testcases-link-display')
		local testcasesLink = makeWikilink(testcasesPage, testcasesDisplay)
		local testcasesEditUrl = testcasesTitle:fullUrl{action = 'edit'}
		local testcasesEditDisplay = message('testcases-edit-link-display')
		local testcasesEditLink = makeUrlLink(testcasesEditUrl, testcasesEditDisplay)
		testcasesLinks = testcasesLink .. ' ' .. makeToolbar(testcasesEditLink)
	else
		local testcasesPreload
		if subjectSpace == 828 then
			testcasesPreload = message('module-testcases-preload')
		else
			testcasesPreload = message('template-testcases-preload')
		end
		local testcasesCreateUrl = testcasesTitle:fullUrl{action = 'edit', preload = testcasesPreload}
		local testcasesCreateDisplay = message('testcases-create-link-display')
		local testcasesCreateLink = makeUrlLink(testcasesCreateUrl, testcasesCreateDisplay)
		testcasesLinks = message('testcases-link-display') .. ' ' .. makeToolbar(testcasesCreateLink)
	end
	local messageName
	if subjectSpace == 828 then
		messageName = 'experiment-blurb-module'
	else
		messageName = 'experiment-blurb-template'
	end
	return message(messageName, {sandboxLinks, testcasesLinks})
end

function p.makeCategoriesBlurb(args, env)
	--[[
	-- Generates the text "Please add categories to the /doc subpage."
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	-- Messages:
	-- 'doc-link-display' --&gt; '/doc'
	-- 'add-categories-blurb' --&gt; 'Please add categories to the $1 subpage.'
	--]]
	local docTitle = env.docTitle
	if not docTitle then
		return nil
	end
	local docPathLink = makeWikilink(docTitle.prefixedText, message('doc-link-display'))
	return message('add-categories-blurb', {docPathLink})
end

function p.makeSubpagesBlurb(args, env)
	--[[
	-- Generates the "Subpages of this template" link.
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	
	-- Messages:
	-- 'template-pagetype' --&gt; 'template'
	-- 'module-pagetype' --&gt; 'module'
	-- 'default-pagetype' --&gt; 'page'
	-- 'subpages-link-display' --&gt; 'Subpages of this $1'
	--]]
	local subjectSpace = env.subjectSpace
	local templateTitle = env.templateTitle
	if not subjectSpace or not templateTitle then
		return nil
	end
	local pagetype
	if subjectSpace == 10 then
		pagetype = message('template-pagetype')
	elseif subjectSpace == 828 then
		pagetype = message('module-pagetype')
	else
		pagetype = message('default-pagetype')
	end
	local subpagesLink = makeWikilink(
		'Special:PrefixIndex/' .. templateTitle.prefixedText .. '/',
		message('subpages-link-display', {pagetype})
	)
	return message('subpages-blurb', {subpagesLink})
end

function p.makePrintBlurb(args, env)
	--[=[
	-- Generates the blurb displayed when there is a print version of the template available.
	-- @args - a table of arguments passed by the user
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	--
	-- Messages:
	-- 'print-link-display' --&gt; '/Print'
	-- 'print-blurb' --&gt; 'A [[Help:Books/for experts#Improving the book layout|print version]]'
	--		.. ' of this template exists at $1.'
	--		.. ' If you make a change to this template, please update the print version as well.'
	-- 'display-print-category' --&gt; true
	-- 'print-category' --&gt; 'Templates with print versions'
	--]=]
	local printTitle = env.printTitle
	if not printTitle then
		return nil
	end
	local ret
	if printTitle.exists then
		local printLink = makeWikilink(printTitle.prefixedText, message('print-link-display'))
		ret = message('print-blurb', {printLink})
		local displayPrintCategory = message('display-print-category', nil, 'boolean')
		if displayPrintCategory then
			ret = ret .. makeCategoryLink(message('print-category'))
		end
	end
	return ret
end

----------------------------------------------------------------------------
-- Tracking categories
----------------------------------------------------------------------------

function p.addTrackingCategories(env)
	--[[
	-- Check if {{documentation}} is transcluded on a /doc or /testcases page.
	-- @env - environment table containing title objects, etc., generated with p.getEnvironment
	
	-- Messages:
	-- 'display-strange-usage-category' --&gt; true
	-- 'doc-subpage' --&gt; 'doc'
	-- 'testcases-subpage' --&gt; 'testcases'
	-- 'strange-usage-category' --&gt; 'Wikipedia pages with strange ((documentation)) usage'
	-- 
	-- /testcases pages in the module namespace are not categorised, as they may have
	-- {{documentation}} transcluded automatically.
	--]]
	local title = env.title
	local subjectSpace = env.subjectSpace
	if not title or not subjectSpace then
		return nil
	end
	local subpage = title.subpageText
	local ret = ''
	if message('display-strange-usage-category', nil, 'boolean')
		and (
			subpage == message('doc-subpage')
			or subjectSpace ~= 828 and subpage == message('testcases-subpage')
		)
	then
		ret = ret .. makeCategoryLink(message('strange-usage-category'))
	end
	return ret
end

return p</text>
    <sha1>5b80b9be06d84932df137c37d640ceb7ddd4fb62</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:Documentation</title>
  <ns>10</ns>
  <id>84</id>
  <revision>
    <id>222</id>
    <timestamp>2016-01-06T06:15:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}&lt;noinclude&gt; &lt;!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --&gt; &lt;/noi..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="182" xml:space="preserve">{{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}&lt;noinclude&gt;
&lt;!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --&gt;
&lt;/noinclude&gt;</text>
    <sha1>ce7fd93f18c46b4fa871bf679afd05cbda72d8c4</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Module:Message box</title>
  <ns>0</ns>
  <id>85</id>
  <revision>
    <id>223</id>
    <timestamp>2016-01-06T06:19:03Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "-- This is a meta-module for producing message box templates, including -- {{mbox}}, {{ambox}}, {{imbox}}, {{tmbox}}, {{ombox}}, {{cmbox}} and {{fmbox}}.  -- Load necessary mo..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16479" xml:space="preserve">-- This is a meta-module for producing message box templates, including
-- {{mbox}}, {{ambox}}, {{imbox}}, {{tmbox}}, {{ombox}}, {{cmbox}} and {{fmbox}}.

-- Load necessary modules.
require('Module:No globals')
local getArgs
local categoryHandler = require('Module:Category handler')._main
local yesno = require('Module:Yesno')

-- Get a language object for formatDate and ucfirst.
local lang = mw.language.getContentLanguage()

--------------------------------------------------------------------------------
-- Helper functions
--------------------------------------------------------------------------------

local function getTitleObject(...)
	-- Get the title object, passing the function through pcall
	-- in case we are over the expensive function count limit.
	local success, title = pcall(mw.title.new, ...)
	if success then
		return title
	end
end

local function union(t1, t2)
	-- Returns the union of two arrays.
	local vals = {}
	for i, v in ipairs(t1) do
		vals[v] = true
	end
	for i, v in ipairs(t2) do
		vals[v] = true
	end
	local ret = {}
	for k in pairs(vals) do
		table.insert(ret, k)
	end
	table.sort(ret)
	return ret
end

local function getArgNums(args, prefix)
	local nums = {}
	for k, v in pairs(args) do
		local num = mw.ustring.match(tostring(k), '^' .. prefix .. '([1-9]%d*)$')
		if num then
			table.insert(nums, tonumber(num))
		end
	end
	table.sort(nums)
	return nums
end

--------------------------------------------------------------------------------
-- Box class definition
--------------------------------------------------------------------------------

local MessageBox = {}
MessageBox.__index = MessageBox

function MessageBox.new(boxType, args, cfg)
	args = args or {}
	local obj = {}

	-- Set the title object and the namespace.
	obj.title = getTitleObject(args.page) or mw.title.getCurrentTitle()

	-- Set the config for our box type.
	obj.cfg = cfg[boxType]
	if not obj.cfg then
		local ns = obj.title.namespace
		-- boxType is "mbox" or invalid input
		if ns == 0 then
			obj.cfg = cfg.ambox -- main namespace
		elseif ns == 6 then
			obj.cfg = cfg.imbox -- file namespace
		elseif ns == 14 then
			obj.cfg = cfg.cmbox -- category namespace
		else
			local nsTable = mw.site.namespaces[ns]
			if nsTable and nsTable.isTalk then
				obj.cfg = cfg.tmbox -- any talk namespace
			else
				obj.cfg = cfg.ombox -- other namespaces or invalid input
			end
		end
	end

	-- Set the arguments, and remove all blank arguments except for the ones
	-- listed in cfg.allowBlankParams.
	do
		local newArgs = {}
		for k, v in pairs(args) do
			if v ~= '' then
				newArgs[k] = v
			end
		end
		for i, param in ipairs(obj.cfg.allowBlankParams or {}) do
			newArgs[param] = args[param]
		end
		obj.args = newArgs
	end

	-- Define internal data structure.
	obj.categories = {}
	obj.classes = {}

	return setmetatable(obj, MessageBox)
end

function MessageBox:addCat(ns, cat, sort)
	if not cat then
		return nil
	end
	if sort then
		cat = string.format('[[Category:%s|%s]]', cat, sort)
	else
		cat = string.format('[[Category:%s]]', cat)
	end
	self.categories[ns] = self.categories[ns] or {}
	table.insert(self.categories[ns], cat)
end

function MessageBox:addClass(class)
	if not class then
		return nil
	end
	table.insert(self.classes, class)
end

function MessageBox:setParameters()
	local args = self.args
	local cfg = self.cfg

	-- Get type data.
	self.type = args.type
	local typeData = cfg.types[self.type]
	self.invalidTypeError = cfg.showInvalidTypeError
		and self.type
		and not typeData
	typeData = typeData or cfg.types[cfg.default]
	self.typeClass = typeData.class
	self.typeImage = typeData.image

	-- Find if the box has been wrongly substituted.
	self.isSubstituted = cfg.substCheck and args.subst == 'SUBST'

	-- Find whether we are using a small message box.
	self.isSmall = cfg.allowSmall and (
		cfg.smallParam and args.small == cfg.smallParam
		or not cfg.smallParam and yesno(args.small)
	)

	-- Add attributes, classes and styles.
	self.id = args.id
	self:addClass(
		cfg.usePlainlinksParam and yesno(args.plainlinks or true) and 'plainlinks'
	)
	for _, class in ipairs(cfg.classes or {}) do
		self:addClass(class)
	end
	if self.isSmall then
		self:addClass(cfg.smallClass or 'mbox-small')
	end
	self:addClass(self.typeClass)
	self:addClass(args.class)
	self.style = args.style
	self.attrs = args.attrs

	-- Set text style.
	self.textstyle = args.textstyle

	-- Find if we are on the template page or not. This functionality is only
	-- used if useCollapsibleTextFields is set, or if both cfg.templateCategory
	-- and cfg.templateCategoryRequireName are set.
	self.useCollapsibleTextFields = cfg.useCollapsibleTextFields
	if self.useCollapsibleTextFields
		or cfg.templateCategory
		and cfg.templateCategoryRequireName
	then
		self.name = args.name
		if self.name then
			local templateName = mw.ustring.match(
				self.name,
				'^[tT][eE][mM][pP][lL][aA][tT][eE][%s_]*:[%s_]*(.*)$'
			) or self.name
			templateName = 'Template:' .. templateName
			self.templateTitle = getTitleObject(templateName)
		end
		self.isTemplatePage = self.templateTitle
			and mw.title.equals(self.title, self.templateTitle)
	end

	-- Process data for collapsible text fields. At the moment these are only
	-- used in {{ambox}}.
	if self.useCollapsibleTextFields then
		-- Get the self.issue value.
		if self.isSmall and args.smalltext then
			self.issue = args.smalltext
		else
			local sect
			if args.sect == '' then
				sect = 'This ' .. (cfg.sectionDefault or 'page')
			elseif type(args.sect) == 'string' then
				sect = 'This ' .. args.sect
			end
			local issue = args.issue
			issue = type(issue) == 'string' and issue ~= '' and issue or nil
			local text = args.text
			text = type(text) == 'string' and text or nil
			local issues = {}
			table.insert(issues, sect)
			table.insert(issues, issue)
			table.insert(issues, text)
			self.issue = table.concat(issues, ' ')
		end

		-- Get the self.talk value.
		local talk = args.talk
		-- Show talk links on the template page or template subpages if the talk
		-- parameter is blank.
		if talk == ''
			and self.templateTitle
			and (
				mw.title.equals(self.templateTitle, self.title)
				or self.title:isSubpageOf(self.templateTitle)
			)
		then
			talk = '#'
		elseif talk == '' then
			talk = nil
		end
		if talk then
			-- If the talk value is a talk page, make a link to that page. Else
			-- assume that it's a section heading, and make a link to the talk
			-- page of the current page with that section heading.
			local talkTitle = getTitleObject(talk)
			local talkArgIsTalkPage = true
			if not talkTitle or not talkTitle.isTalkPage then
				talkArgIsTalkPage = false
				talkTitle = getTitleObject(
					self.title.text,
					mw.site.namespaces[self.title.namespace].talk.id
				)
			end
			if talkTitle and talkTitle.exists then
				local talkText = 'Relevant discussion may be found on'
				if talkArgIsTalkPage then
					talkText = string.format(
						'%s [[%s|%s]].',
						talkText,
						talk,
						talkTitle.prefixedText
					)
				else
					talkText = string.format(
						'%s the [[%s#%s|talk page]].',
						talkText,
						talkTitle.prefixedText,
						talk
					)
				end
				self.talk = talkText
			end
		end

		-- Get other values.
		self.fix = args.fix ~= '' and args.fix or nil
		local date
		if args.date and args.date ~= '' then
			date = args.date
		elseif args.date == '' and self.isTemplatePage then
			date = lang:formatDate('F Y')
		end
		if date then
			self.date = string.format(" &lt;small&gt;''(%s)''&lt;/small&gt;", date)
		end
		self.info = args.info
	end

	-- Set the non-collapsible text field. At the moment this is used by all box
	-- types other than ambox, and also by ambox when small=yes.
	if self.isSmall then
		self.text = args.smalltext or args.text
	else
		self.text = args.text
	end

	-- Set the below row.
	self.below = cfg.below and args.below

	-- General image settings.
	self.imageCellDiv = not self.isSmall and cfg.imageCellDiv
	self.imageEmptyCell = cfg.imageEmptyCell
	if cfg.imageEmptyCellStyle then
		self.imageEmptyCellStyle = 'border:none;padding:0px;width:1px'
	end

	-- Left image settings.
	local imageLeft = self.isSmall and args.smallimage or args.image
	if cfg.imageCheckBlank and imageLeft ~= 'blank' and imageLeft ~= 'none'
		or not cfg.imageCheckBlank and imageLeft ~= 'none'
	then
		self.imageLeft = imageLeft
		if not imageLeft then
			local imageSize = self.isSmall
				and (cfg.imageSmallSize or '30x30px')
				or '40x40px'
			self.imageLeft = string.format('[[File:%s|%s|link=|alt=]]', self.typeImage
				or 'Imbox notice.png', imageSize)
		end
	end

	-- Right image settings.
	local imageRight = self.isSmall and args.smallimageright or args.imageright
	if not (cfg.imageRightNone and imageRight == 'none') then
		self.imageRight = imageRight
	end
end

function MessageBox:setMainspaceCategories()
	local args = self.args
	local cfg = self.cfg

	if not cfg.allowMainspaceCategories then
		return nil
	end

	local nums = {}
	for _, prefix in ipairs{'cat', 'category', 'all'} do
		args[prefix .. '1'] = args[prefix]
		nums = union(nums, getArgNums(args, prefix))
	end

	-- The following is roughly equivalent to the old {{Ambox/category}}.
	local date = args.date
	date = type(date) == 'string' and date
	local preposition = 'from'
	for _, num in ipairs(nums) do
		local mainCat = args['cat' .. tostring(num)]
			or args['category' .. tostring(num)]
		local allCat = args['all' .. tostring(num)]
		mainCat = type(mainCat) == 'string' and mainCat
		allCat = type(allCat) == 'string' and allCat
		if mainCat and date and date ~= '' then
			local catTitle = string.format('%s %s %s', mainCat, preposition, date)
			self:addCat(0, catTitle)
			catTitle = getTitleObject('Category:' .. catTitle)
			if not catTitle or not catTitle.exists then
				self:addCat(0, 'Articles with invalid date parameter in template')
			end
		elseif mainCat and (not date or date == '') then
			self:addCat(0, mainCat)
		end
		if allCat then
			self:addCat(0, allCat)
		end
	end
end

function MessageBox:setTemplateCategories()
	local args = self.args
	local cfg = self.cfg

	-- Add template categories.
	if cfg.templateCategory then
		if cfg.templateCategoryRequireName then
			if self.isTemplatePage then
				self:addCat(10, cfg.templateCategory)
			end
		elseif not self.title.isSubpage then
			self:addCat(10, cfg.templateCategory)
		end
	end

	-- Add template error categories.
	if cfg.templateErrorCategory then
		local templateErrorCategory = cfg.templateErrorCategory
		local templateCat, templateSort
		if not self.name and not self.title.isSubpage then
			templateCat = templateErrorCategory
		elseif self.isTemplatePage then
			local paramsToCheck = cfg.templateErrorParamsToCheck or {}
			local count = 0
			for i, param in ipairs(paramsToCheck) do
				if not args[param] then
					count = count + 1
				end
			end
			if count &gt; 0 then
				templateCat = templateErrorCategory
				templateSort = tostring(count)
			end
			if self.categoryNums and #self.categoryNums &gt; 0 then
				templateCat = templateErrorCategory
				templateSort = 'C'
			end
		end
		self:addCat(10, templateCat, templateSort)
	end
end

function MessageBox:setAllNamespaceCategories()
	-- Set categories for all namespaces.
	if self.invalidTypeError then
		local allSort = (self.title.namespace == 0 and 'Main:' or '') .. self.title.prefixedText
		self:addCat('all', 'Wikipedia message box parameter needs fixing', allSort)
	end
	if self.isSubstituted then
		self:addCat('all', 'Pages with incorrectly substituted templates')
	end
end

function MessageBox:setCategories()
	if self.title.namespace == 0 then
		self:setMainspaceCategories()
	elseif self.title.namespace == 10 then
		self:setTemplateCategories()
	end
	self:setAllNamespaceCategories()
end

function MessageBox:renderCategories()
	-- Convert category tables to strings and pass them through
	-- [[Module:Category handler]].
	return categoryHandler{
		main = table.concat(self.categories[0] or {}),
		template = table.concat(self.categories[10] or {}),
		all = table.concat(self.categories.all or {}),
		nocat = self.args.nocat,
		page = self.args.page
	}
end

function MessageBox:export()
	local root = mw.html.create()

	-- Add the subst check error.
	if self.isSubstituted and self.name then
		root:tag('b')
			:addClass('error')
			:wikitext(string.format(
				'Template &lt;code&gt;%s[[Template:%s|%s]]%s&lt;/code&gt; has been incorrectly substituted.',
				mw.text.nowiki('{{'), self.name, self.name, mw.text.nowiki('}}')
			))
	end

	-- Create the box table.
	local boxTable = root:tag('table')
	boxTable:attr('id', self.id or nil)
	for i, class in ipairs(self.classes or {}) do
		boxTable:addClass(class or nil)
	end
	boxTable
		:cssText(self.style or nil)
		:attr('role', 'presentation')

	if self.attrs then
		boxTable:attr(self.attrs)
	end

	-- Add the left-hand image.
	local row = boxTable:tag('tr')
	if self.imageLeft then
		local imageLeftCell = row:tag('td'):addClass('mbox-image')
		if self.imageCellDiv then
			-- If we are using a div, redefine imageLeftCell so that the image
			-- is inside it. Divs use style="width: 52px;", which limits the
			-- image width to 52px. If any images in a div are wider than that,
			-- they may overlap with the text or cause other display problems.
			imageLeftCell = imageLeftCell:tag('div'):css('width', '52px')
		end
		imageLeftCell:wikitext(self.imageLeft or nil)
	elseif self.imageEmptyCell then
		-- Some message boxes define an empty cell if no image is specified, and
		-- some don't. The old template code in templates where empty cells are
		-- specified gives the following hint: "No image. Cell with some width
		-- or padding necessary for text cell to have 100% width."
		row:tag('td')
			:addClass('mbox-empty-cell')
			:cssText(self.imageEmptyCellStyle or nil)
	end

	-- Add the text.
	local textCell = row:tag('td'):addClass('mbox-text')
	if self.useCollapsibleTextFields then
		-- The message box uses advanced text parameters that allow things to be
		-- collapsible. At the moment, only ambox uses this.
		textCell:cssText(self.textstyle or nil)
		local textCellSpan = textCell:tag('span')
		textCellSpan
			:addClass('mbox-text-span')
			:wikitext(self.issue or nil)
		if not self.isSmall then
			textCellSpan:tag('span')
				:addClass('hide-when-compact')
				:wikitext(self.talk and (' ' .. self.talk) or nil)
				:wikitext(self.fix and (' ' .. self.fix) or nil)
		end
		textCellSpan:wikitext(self.date and (' ' .. self.date) or nil)
		if not self.isSmall then
			textCellSpan
				:tag('span')
				:addClass('hide-when-compact')
				:wikitext(self.info and (' ' .. self.info) or nil)
		end
	else
		-- Default text formatting - anything goes.
		textCell
			:cssText(self.textstyle or nil)
			:wikitext(self.text or nil)
	end

	-- Add the right-hand image.
	if self.imageRight then
		local imageRightCell = row:tag('td'):addClass('mbox-imageright')
		if self.imageCellDiv then
			-- If we are using a div, redefine imageRightCell so that the image
			-- is inside it.
			imageRightCell = imageRightCell:tag('div'):css('width', '52px')
		end
		imageRightCell
			:wikitext(self.imageRight or nil)
	end

	-- Add the below row.
	if self.below then
		boxTable:tag('tr')
			:tag('td')
				:attr('colspan', self.imageRight and '3' or '2')
				:addClass('mbox-text')
				:cssText(self.textstyle or nil)
				:wikitext(self.below or nil)
	end

	-- Add error message for invalid type parameters.
	if self.invalidTypeError then
		root:tag('div')
			:css('text-align', 'center')
			:wikitext(string.format(
				'This message box is using an invalid "type=%s" parameter and needs fixing.',
				self.type or ''
			))
	end

	-- Add categories.
	root:wikitext(self:renderCategories() or nil)

	return tostring(root)
end

--------------------------------------------------------------------------------
-- Exports
--------------------------------------------------------------------------------

local p, mt = {}, {}

function p._exportClasses()
	-- For testing.
	return {
		MessageBox = MessageBox
	}
end

function p.main(boxType, args, cfgTables)
	local box = MessageBox.new(boxType, args, cfgTables or mw.loadData('Module:Message box/configuration'))
	box:setParameters()
	box:setCategories()
	return box:export()
end

function mt.__index(t, k)
	return function (frame)
		if not getArgs then
			getArgs = require('Module:Arguments').getArgs
		end
		return t.main(k, getArgs(frame, {trim = false, removeBlanks = false}))
	end
end

return setmetatable(p, mt)</text>
    <sha1>0e1b08d466f6c7979b1f95f3ad403fbd4998209c</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Module:Documentation/config</title>
  <ns>0</ns>
  <id>86</id>
  <revision>
    <id>224</id>
    <timestamp>2016-01-06T06:25:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "---------------------------------------------------------------------------------------------------- -- --                               Configuration for Module:Documentation..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19013" xml:space="preserve">----------------------------------------------------------------------------------------------------
--
--                               Configuration for Module:Documentation
--
-- Here you can set the values of the parameters and messages used in Module:Documentation to
-- localise it to your wiki and your language. Unless specified otherwise, values given here
-- should be string values.
----------------------------------------------------------------------------------------------------

local cfg = {} -- Do not edit this line.

----------------------------------------------------------------------------------------------------
-- Protection template configuration
----------------------------------------------------------------------------------------------------

-- cfg['protection-template']
-- The name of the template that displays the protection icon (a padlock on enwiki).
cfg['protection-template'] = 'pp-template'

-- cfg['protection-reason-edit']
-- The protection reason for edit-protected templates to pass to
-- [[Module:Protection banner]].
cfg['protection-reason-edit'] = 'template'

--[[
-- cfg['protection-template-args']
-- Any arguments to send to the protection template. This should be a Lua table.
-- For example, if the protection template is "pp-template", and the wikitext template invocation
-- looks like "{{pp-template|docusage=yes}}", then this table should look like "{docusage = 'yes'}".
 --]]
 cfg['protection-template-args'] = {docusage = 'yes'}

--[[
----------------------------------------------------------------------------------------------------
-- Sandbox notice configuration
--
-- On sandbox pages the module can display a template notifying users that the current page is a
-- sandbox, and the location of test cases pages, etc. The module decides whether the page is a
-- sandbox or not based on the value of cfg['sandbox-subpage']. The following settings configure the
-- messages that the notices contains.
----------------------------------------------------------------------------------------------------
--]]

-- cfg['sandbox-notice-image']
-- The image displayed in the sandbox notice.
cfg['sandbox-notice-image'] = '[[Image:Sandbox.svg|50px|alt=|link=]]'

--[[
-- cfg['sandbox-notice-pagetype-template']
-- cfg['sandbox-notice-pagetype-module']
-- cfg['sandbox-notice-pagetype-other']
-- The page type of the sandbox page. The message that is displayed depends on the current subject
-- namespace. This message is used in either cfg['sandbox-notice-blurb'] or
-- cfg['sandbox-notice-diff-blurb'].
--]]
cfg['sandbox-notice-pagetype-template'] = '[[Wikipedia:Template test cases|template sandbox]] page'
cfg['sandbox-notice-pagetype-module'] = '[[Wikipedia:Template test cases|module sandbox]] page'
cfg['sandbox-notice-pagetype-other'] = 'sandbox page'

--[[
-- cfg['sandbox-notice-blurb']
-- cfg['sandbox-notice-diff-blurb']
-- cfg['sandbox-notice-diff-display']
-- Either cfg['sandbox-notice-blurb'] or cfg['sandbox-notice-diff-blurb'] is the opening sentence
-- of the sandbox notice. The latter has a diff link, but the former does not. $1 is the page
-- type, which is either cfg['sandbox-notice-pagetype-template'],
-- cfg['sandbox-notice-pagetype-module'] or cfg['sandbox-notice-pagetype-other'] depending what
-- namespace we are in. $2 is a link to the main template page, and $3 is a diff link between
-- the sandbox and the main template. The display value of the diff link is set by 
-- cfg['sandbox-notice-compare-link-display'].
--]]
cfg['sandbox-notice-blurb'] = 'This is the $1 for $2.'
cfg['sandbox-notice-diff-blurb'] = 'This is the $1 for $2 ($3).'
cfg['sandbox-notice-compare-link-display'] = 'diff'

--[[
-- cfg['sandbox-notice-testcases-blurb']
-- cfg['sandbox-notice-testcases-link-display']
-- cfg['sandbox-notice-testcases-run-blurb']
-- cfg['sandbox-notice-testcases-run-link-display']
-- cfg['sandbox-notice-testcases-blurb'] is a sentence notifying the user that there is a test cases page
-- corresponding to this sandbox that they can edit. $1 is a link to the test cases page.
-- cfg['sandbox-notice-testcases-link-display'] is the display value for that link.
-- cfg['sandbox-notice-testcases-run-blurb'] is a sentence notifying the user that there is a test cases page
-- corresponding to this sandbox that they can edit, along with a link to run it. $1 is a link to the test
-- cases page, and $2 is a link to the page to run it.
-- cfg['sandbox-notice-testcases-run-link-display'] is the display value for the link to run the test
-- cases.
--]]
cfg['sandbox-notice-testcases-blurb'] = 'See also the companion subpage for $1.'
cfg['sandbox-notice-testcases-link-display'] = 'test cases'
cfg['sandbox-notice-testcases-run-blurb'] = 'See also the companion subpage for $1 ($2).'
cfg['sandbox-notice-testcases-run-link-display'] = 'run'

-- cfg['sandbox-category']
-- A category to add to all template sandboxes.
cfg['sandbox-category'] = 'Template sandboxes'

----------------------------------------------------------------------------------------------------
-- Start box configuration
----------------------------------------------------------------------------------------------------

-- cfg['documentation-icon-wikitext']
-- The wikitext for the icon shown at the top of the template.
cfg['documentation-icon-wikitext'] = '[[File:Test Template Info-Icon - Version (2).svg|50px|link=|alt=Documentation icon]]'

-- cfg['template-namespace-heading']
-- The heading shown in the template namespace.
cfg['template-namespace-heading'] = 'Template documentation'

-- cfg['module-namespace-heading']
-- The heading shown in the module namespace.
cfg['module-namespace-heading'] = 'Module documentation'

-- cfg['file-namespace-heading']
-- The heading shown in the file namespace.
cfg['file-namespace-heading'] = 'Summary'

-- cfg['other-namespaces-heading']
-- The heading shown in other namespaces.
cfg['other-namespaces-heading'] = 'Documentation'

-- cfg['view-link-display']
-- The text to display for "view" links.
cfg['view-link-display'] = 'view'

-- cfg['edit-link-display']
-- The text to display for "edit" links.
cfg['edit-link-display'] = 'edit'

-- cfg['history-link-display']
-- The text to display for "history" links.
cfg['history-link-display'] = 'history'

-- cfg['purge-link-display']
-- The text to display for "purge" links.
cfg['purge-link-display'] = 'purge'

-- cfg['create-link-display']
-- The text to display for "create" links.
cfg['create-link-display'] = 'create'

----------------------------------------------------------------------------------------------------
-- Link box (end box) configuration
----------------------------------------------------------------------------------------------------

-- cfg['transcluded-from-blurb']
-- Notice displayed when the docs are transcluded from another page. $1 is a wikilink to that page.
cfg['transcluded-from-blurb'] = 'The above [[Wikipedia:Template documentation|documentation]] is [[Wikipedia:Transclusion|transcluded]] from $1.'

--[[
-- cfg['create-module-doc-blurb']
-- Notice displayed in the module namespace when the documentation subpage does not exist.
-- $1 is a link to create the documentation page with the preload cfg['module-preload'] and the
-- display cfg['create-link-display'].
--]]
cfg['create-module-doc-blurb'] = 'You might want to $1 a documentation page for this [[Wikipedia:Lua|Scribunto module]].'

----------------------------------------------------------------------------------------------------
-- Experiment blurb configuration
----------------------------------------------------------------------------------------------------

--[[
-- cfg['experiment-blurb-template']
-- cfg['experiment-blurb-module']
-- The experiment blurb is the text inviting editors to experiment in sandbox and test cases pages.
-- It is only shown in the template and module namespaces. With the default English settings, it
-- might look like this:
--
-- Editors can experiment in this template's sandbox (edit | diff) and testcases (edit) pages.
--
-- In this example, "sandbox", "edit", "diff", "testcases", and "edit" would all be links.
--
-- There are two versions, cfg['experiment-blurb-template'] and cfg['experiment-blurb-module'], depending
-- on what namespace we are in.
-- 
-- Parameters:
--
-- $1 is a link to the sandbox page. If the sandbox exists, it is in the following format:
--
--     cfg['sandbox-link-display'] (cfg['sandbox-edit-link-display'] | cfg['compare-link-display'])
-- 
-- If the sandbox doesn't exist, it is in the format:
--
--     cfg['sandbox-link-display'] (cfg['sandbox-create-link-display'] | cfg['mirror-link-display'])
-- 
-- The link for cfg['sandbox-create-link-display'] link preloads the page with cfg['template-sandbox-preload']
-- or cfg['module-sandbox-preload'], depending on the current namespace. The link for cfg['mirror-link-display']
-- loads a default edit summary of cfg['mirror-edit-summary'].
--
-- $2 is a link to the test cases page. If the test cases page exists, it is in the following format:
--
--     cfg['testcases-link-display'] (cfg['testcases-edit-link-display'])
--
-- If the test cases page doesn't exist, it is in the format:
-- 
--     cfg['testcases-link-display'] (cfg['testcases-create-link-display'])
--
-- If the test cases page doesn't exist, the link for cfg['testcases-create-link-display'] preloads the
-- page with cfg['template-testcases-preload'] or cfg['module-testcases-preload'], depending on the current
-- namespace.
--]]
cfg['experiment-blurb-template'] = "Editors can experiment in this template's $1 and $2 pages."
cfg['experiment-blurb-module'] = "Editors can experiment in this module's $1 and $2 pages."

----------------------------------------------------------------------------------------------------
-- Sandbox link configuration
----------------------------------------------------------------------------------------------------

-- cfg['sandbox-subpage']
-- The name of the template subpage typically used for sandboxes.
cfg['sandbox-subpage'] = 'sandbox'

-- cfg['template-sandbox-preload']
-- Preload file for template sandbox pages.
cfg['template-sandbox-preload'] = 'Template:Documentation/preload-sandbox'

-- cfg['module-sandbox-preload']
-- Preload file for Lua module sandbox pages.
cfg['module-sandbox-preload'] = 'Template:Documentation/preload-module-sandbox'

-- cfg['sandbox-link-display']
-- The text to display for "sandbox" links.
cfg['sandbox-link-display'] = 'sandbox'

-- cfg['sandbox-edit-link-display']
-- The text to display for sandbox "edit" links.
cfg['sandbox-edit-link-display'] = 'edit'

-- cfg['sandbox-create-link-display']
-- The text to display for sandbox "create" links.
cfg['sandbox-create-link-display'] = 'create'

-- cfg['compare-link-display']
-- The text to display for "compare" links.
cfg['compare-link-display'] = 'diff'

-- cfg['mirror-edit-summary']
-- The default edit summary to use when a user clicks the "mirror" link. $1 is a wikilink to the
-- template page.
cfg['mirror-edit-summary'] = 'Create sandbox version of $1'

-- cfg['mirror-link-display']
-- The text to display for "mirror" links.
cfg['mirror-link-display'] = 'mirror'

-- cfg['mirror-link-preload']
-- The page to preload when a user clicks the "mirror" link.
cfg['mirror-link-preload'] = 'Template:Documentation/mirror'

----------------------------------------------------------------------------------------------------
-- Test cases link configuration
----------------------------------------------------------------------------------------------------

-- cfg['testcases-subpage']
-- The name of the template subpage typically used for test cases.
cfg['testcases-subpage'] = 'testcases'

-- cfg['template-testcases-preload']
-- Preload file for template test cases pages.
cfg['template-testcases-preload'] = 'Template:Documentation/preload-testcases'

-- cfg['module-testcases-preload']
-- Preload file for Lua module test cases pages.
cfg['module-testcases-preload'] = 'Template:Documentation/preload-module-testcases'

-- cfg['testcases-link-display']
-- The text to display for "testcases" links.
cfg['testcases-link-display'] = 'testcases'

-- cfg['testcases-edit-link-display']
-- The text to display for test cases "edit" links.
cfg['testcases-edit-link-display'] = 'edit'

-- cfg['testcases-create-link-display']
-- The text to display for test cases "create" links.
cfg['testcases-create-link-display'] = 'create'

----------------------------------------------------------------------------------------------------
-- Add categories blurb configuration
----------------------------------------------------------------------------------------------------

--[[
-- cfg['add-categories-blurb']
-- Text to direct users to add categories to the /doc subpage. Not used if the "content" or
-- "docname fed" arguments are set, as then it is not clear where to add the categories. $1 is a
-- link to the /doc subpage with a display value of cfg['doc-link-display'].
--]]
cfg['add-categories-blurb'] = 'Please add categories to the $1 subpage.'

-- cfg['doc-link-display']
-- The text to display when linking to the /doc subpage.
cfg['doc-link-display'] = '/doc'

----------------------------------------------------------------------------------------------------
-- Subpages link configuration
----------------------------------------------------------------------------------------------------

--[[
-- cfg['subpages-blurb']
-- The "Subpages of this template" blurb. $1 is a link to the main template's subpages with a
-- display value of cfg['subpages-link-display']. In the English version this blurb is simply
-- the link followed by a period, and the link display provides the actual text.
--]]
cfg['subpages-blurb'] = '$1.'

--[[
-- cfg['subpages-link-display']
-- The text to display for the "subpages of this page" link. $1 is cfg['template-pagetype'],
-- cfg['module-pagetype'] or cfg['default-pagetype'], depending on whether the current page is in
-- the template namespace, the module namespace, or another namespace.
--]]
cfg['subpages-link-display'] = 'Subpages of this $1'

-- cfg['template-pagetype']
-- The pagetype to display for template pages.
cfg['template-pagetype'] = 'template'

-- cfg['module-pagetype']
-- The pagetype to display for Lua module pages.
cfg['module-pagetype'] = 'module'

-- cfg['default-pagetype']
-- The pagetype to display for pages other than templates or Lua modules.
cfg['default-pagetype'] = 'page'

----------------------------------------------------------------------------------------------------
-- Doc link configuration
----------------------------------------------------------------------------------------------------

-- cfg['doc-subpage']
-- The name of the subpage typically used for documentation pages.
cfg['doc-subpage'] = 'doc'

-- cfg['file-docpage-preload']
-- Preload file for documentation page in the file namespace.
cfg['file-docpage-preload'] = 'Template:Documentation/preload-filespace'

-- cfg['docpage-preload']
-- Preload file for template documentation pages in all namespaces.
cfg['docpage-preload'] = 'Template:Documentation/preload'

-- cfg['module-preload']
-- Preload file for Lua module documentation pages.
cfg['module-preload'] = 'Template:Documentation/preload-module-doc'

----------------------------------------------------------------------------------------------------
-- Print version configuration
----------------------------------------------------------------------------------------------------

-- cfg['print-subpage']
-- The name of the template subpage used for print versions.
cfg['print-subpage'] = 'Print'

-- cfg['print-link-display']
-- The text to display when linking to the /Print subpage.
cfg['print-link-display'] = '/Print'

-- cfg['print-blurb']
-- Text to display if a /Print subpage exists. $1 is a link to the subpage with a display value of cfg['print-link-display'].
cfg['print-blurb'] = 'A [[Help:Books/for experts#Improving the book layout|print version]] of this template exists at $1.'
	.. ' If you make a change to this template, please update the print version as well.'

-- cfg['display-print-category']
-- Set to true to enable output of cfg['print-category'] if a /Print subpage exists.
-- This should be a boolean value (either true or false).
cfg['display-print-category'] = true

-- cfg['print-category']
-- Category to output if cfg['display-print-category'] is set to true, and a /Print subpage exists.
cfg['print-category'] = 'Templates with print versions'

----------------------------------------------------------------------------------------------------
-- HTML and CSS configuration
----------------------------------------------------------------------------------------------------

-- cfg['main-div-id']
-- The "id" attribute of the main HTML "div" tag.
cfg['main-div-id'] = 'template-documentation'

-- cfg['main-div-classes']
-- The CSS classes added to the main HTML "div" tag.
cfg['main-div-classes'] = 'template-documentation iezoomfix'

-- cfg['start-box-linkclasses']
-- The CSS classes used for the [view][edit][history] or [create] links in the start box.
cfg['start-box-linkclasses'] = 'mw-editsection-like plainlinks'

-- cfg['start-box-link-id']
-- The HTML "id" attribute for the links in the start box.
cfg['start-box-link-id'] = 'doc_editlinks'

----------------------------------------------------------------------------------------------------
-- {{fmbox}} template configuration
----------------------------------------------------------------------------------------------------

-- cfg['fmbox-id']
-- The id sent to the "id" parameter of the {{fmbox}} template.
cfg['fmbox-id'] = 'documentation-meta-data'

-- cfg['fmbox-style']
-- The value sent to the style parameter of {{fmbox}}.
cfg['fmbox-style'] = 'background-color: #ecfcf4'

-- cfg['fmbox-textstyle']
-- The value sent to the "textstyle parameter of {{fmbox}}.
cfg['fmbox-textstyle'] = 'font-style: italic'

----------------------------------------------------------------------------------------------------
-- Tracking category configuration
----------------------------------------------------------------------------------------------------

-- cfg['display-strange-usage-category']
-- Set to true to enable output of cfg['strange-usage-category'] if the module is used on a /doc subpage
-- or a /testcases subpage. This should be a boolean value (either true or false).
cfg['display-strange-usage-category'] = true

-- cfg['strange-usage-category']
-- Category to output if cfg['display-strange-usage-category'] is set to true and the module is used on a
-- /doc subpage or a /testcases subpage.
cfg['strange-usage-category'] = 'Wikipedia pages with strange ((documentation)) usage'

--[[
----------------------------------------------------------------------------------------------------
-- End configuration
--
-- Don't edit anything below this line.
----------------------------------------------------------------------------------------------------
--]]

return cfg</text>
    <sha1>39bcf8bd16bb48d808a82e405d7bc45608ba8ef7</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Module:Yesno</title>
  <ns>0</ns>
  <id>87</id>
  <revision>
    <id>225</id>
    <timestamp>2016-01-06T06:27:48Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "-- Function allowing for consistent treatment of boolean-like wikitext input. -- It works similarly to the template {{yesno}}.  return function (val, default) 	-- If your wiki..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="710" xml:space="preserve">-- Function allowing for consistent treatment of boolean-like wikitext input.
-- It works similarly to the template {{yesno}}.

return function (val, default)
	-- If your wiki uses non-ascii characters for any of "yes", "no", etc., you
	-- should replace "val:lower()" with "mw.ustring.lower(val)" in the
	-- following line.
	val = type(val) == 'string' and val:lower() or val
	if val == nil then
		return nil
	elseif val == true 
		or val == 'yes'
		or val == 'y'
		or val == 'true'
		or val == 't'
		or tonumber(val) == 1
	then
		return true
	elseif val == false
		or val == 'no'
		or val == 'n'
		or val == 'false'
		or val == 'f'
		or tonumber(val) == 0
	then
		return false
	else
		return default
	end
end</text>
    <sha1>12981c9a31eb2b0af1be4f16fc0642e180eac8c2</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:Gitblit</title>
  <ns>10</ns>
  <id>88</id>
  <revision>
    <id>226</id>
    <timestamp>2016-01-06T06:31:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Git repo |project={{{3|mediawiki/extensions/}}}{{{1|}}} |text={{{2|{{{1}}}}}}}}&lt;noinclude&gt; {{doc}} &lt;/noinclude&gt;"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="113" xml:space="preserve">{{Git repo |project={{{3|mediawiki/extensions/}}}{{{1|}}} |text={{{2|{{{1}}}}}}}}&lt;noinclude&gt;
{{doc}}
&lt;/noinclude&gt;</text>
    <sha1>0b3740435275fd4e817a874bd7b77235822e64da</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:Doc</title>
  <ns>10</ns>
  <id>89</id>
  <revision>
    <id>227</id>
    <timestamp>2016-01-06T06:32:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt;{{Documentation subpage}} {{timw|{{BASEPAGENAME}}}} &lt;/noinclude&gt; ''Deprecated, use {{tl|git repo}} instead.''  Generates a link to a repository's summary page. This..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1163" xml:space="preserve">&lt;noinclude&gt;{{Documentation subpage}}
{{timw|{{BASEPAGENAME}}}}
&lt;/noinclude&gt;
''Deprecated, use {{tl|git repo}} instead.''

Generates a link to a repository's summary page. This invokes {{tl|Git repo}} with logic to just provide an extension name instead.

We are deprecating Gitblit at git.wikimedia.org in favor of [[Diffusion]] ([[phab:T108864]]), so this template's name is misleading.

==Usage==
;Params:
* $1: extension or repository name, defaults to empty string. ''no leading whitespace''
* $2: link text, defaults to $1
* $3: path to the repo including trailing /, defaults to mediawiki/extensions/

==Example==
{{tlx|Gitblit|examples}}
: generates {{Gitblit|examples}}

&lt;!-- tlx *GARBLES and OMITS* the deliberately missing 2nd parameter, so insert space! --&gt;
{{tlx|gitblit|browsertests|&amp;nbsp;|qa/}}
: generates {{gitblit|browsertests| |qa/}}

{{tlx|gitblit|browsertests|Our browsertests repository|qa/}}
: generates {{gitblit|browsertests|Our browsertests repository|qa/}}

&lt;includeonly&gt;
&lt;!-- PUT HERE THE CATEGORIES OF THE TEMPLATE --&gt;
[[Category:Extension templates{{translation}}]]
{{Category|External link templates}}
[[Category:Git]]
&lt;/includeonly&gt;</text>
    <sha1>ae371cddb9056df1f3f06546e9979f992008a52e</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:Git repo</title>
  <ns>10</ns>
  <id>90</id>
  <revision>
    <id>228</id>
    <timestamp>2016-01-06T06:32:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[https://phabricator.wikimedia.org/diffusion/{{#invoke:callsigns|repoToCallsign|{{{project|mediawiki/core}}}}}/ {{#if:{{{text|}}}   |{{{text}}}   |{{{project|MW core}}} }}]&lt;no..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="214" xml:space="preserve">[https://phabricator.wikimedia.org/diffusion/{{#invoke:callsigns|repoToCallsign|{{{project|mediawiki/core}}}}}/ {{#if:{{{text|}}}
  |{{{text}}}
  |{{{project|MW core}}}
}}]&lt;noinclude&gt;
{{draft}}
{{doc}}
&lt;/noinclude&gt;</text>
    <sha1>57544e2c2a10bd4e771081d9355d17acb8c0de9a</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:Tlx</title>
  <ns>10</ns>
  <id>91</id>
  <revision>
    <id>229</id>
    <timestamp>2016-01-06T06:33:47Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{[[{{#if:{{{SISTER|}}}|{{{SISTER}}}Template|{{ns:Template}}}}:{{{1|Tlx}}}|{{{1|Tlx}}}]]&lt;!-- --&gt;{{#if:{{{2|}}}|&amp;#124;{{{2}}}}}&lt;!-- --&gt;{{#if:{{{3|}}}|&amp;#124;{{{3}}}}}&lt;!-- --&gt;{{#..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="398" xml:space="preserve">{{[[{{#if:{{{SISTER|}}}|{{{SISTER}}}Template|{{ns:Template}}}}:{{{1|Tlx}}}|{{{1|Tlx}}}]]&lt;!--
--&gt;{{#if:{{{2|}}}|&amp;#124;{{{2}}}}}&lt;!--
--&gt;{{#if:{{{3|}}}|&amp;#124;{{{3}}}}}&lt;!--
--&gt;{{#if:{{{4|}}}|&amp;#124;{{{4}}}}}&lt;!--
--&gt;{{#if:{{{5|}}}|&amp;#124;{{{5}}}}}&lt;!--
--&gt;{{#if:{{{6|}}}|&amp;#124;{{{6}}}}}&lt;!--
--&gt;{{#if:{{{7|}}}|&amp;#124;{{{7}}}}}&lt;!--
--&gt;{{#if:{{{8|}}}|&amp;#124;''...''}}}}&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>31fa8846f3adf381b3a4943183ffd00c2489a2ff</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Diffusion</title>
  <ns>0</ns>
  <id>92</id>
  <revision>
    <id>230</id>
    <timestamp>2016-01-06T06:35:28Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with ""Diffusion" is the Phabricator repository browser[1] and repository management tool.  Diffusion is integrated with the other tools in the Phabricator suite. For instance:  Whe..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2017" xml:space="preserve">"Diffusion" is the Phabricator repository browser[1] and repository management tool.

Diffusion is integrated with the other tools in the Phabricator suite. For instance:
 When you commit Differential revisions to a tracked repository, they are automatically updated and linked to the corresponding commits;
 You can add Herald rules to notify you about commits that match certain rules;
 In tasks and other places, you can automatically link to commits.

 Creating and managing repositories 
The #Repository-Admins group in Phabricator is tasked with creating, managing and organizing our repositories. If you need help with a repo, these are the folks to ask.

 Requesting a new repository 
If you would like to have a new repository created and/or imported into Diffusion, please create a task in the #Repository-Admins project.

Please include the following information:
 The desired callsign (following the naming conventions), eg: rECNO
 The desired full name, eg: extension-CentralNotice
 If needed, the url to another git repo that you would like the new repository to be populated with initially

Callsigns

Callsigns are short names that represent a repository. You can read more about them in the upstream Phabricator documentation. Callsigns must be only capital Latin alphabet letters (eg: [A-Z]+). They are also immutable (not changeable).

 Callsign templates 
Module:Callsigns maps repository "paths" in gerrit to Diffusion callsigns, for example "mediawiki/extensions/AbuseFilter" maps to the callsign EABF.

{{git file}} takes a project=path/to/repo parameter to refer to a git repository (phab:T101358), so it invokes Module:Callsigns to create a link to a file in diffusion.

 FYI - Email address privacy 

Obviously, if you make a commit using an email address that is associated with a Phabricator user, the user and the email address will be linked in the user interface.

 References 
↑  Upstream documentation on Diffusion: https://secure.phabricator.com/book/phabricator/article/diffusion/</text>
    <sha1>aa34ab63140340d9c519c107ca33a23da7d8ac47</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Template:Git file</title>
  <ns>10</ns>
  <id>93</id>
  <revision>
    <id>231</id>
    <timestamp>2016-01-06T06:37:04Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[https://phabricator.wikimedia.org/diffusion/{{#invoke:callsigns|repoToCallsign|{{{project|mediawiki/core}}}}}/{{#switch:{{{action|}}}   |raw|tree|blame|browse=browse   |#defa..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="943" xml:space="preserve">[https://phabricator.wikimedia.org/diffusion/{{#invoke:callsigns|repoToCallsign|{{{project|mediawiki/core}}}}}/{{#switch:{{{action|}}}
  |raw|tree|blame|browse=browse
  |#default= {{{action|browse}}}
}}/{{#if:{{{branch|}}}
  |{{#ifeq:{{{branch|}}}|HEAD|master|{{{branch}}}}}
  |master
}}/{{{file|}}}{{#if:{{{line|}}}
  |${{{line}}}
}}{{#ifeq:{{{action|}}}|raw
  |?view=raw
  |
}}{{#ifeq:{{{action|}}}|blame
  |?blame=1
  |
}} {{#if:{{{text|}}}
  |{{{text}}}
  |{{{file}}}
}}]&lt;!--
--&gt;{{#ifeq:{{{action|}}}|blob_plain
  |&lt;span style="display:none"&gt;[[Template:Git file/blob_plain]]&lt;/span&gt;}}&lt;!--
--&gt;{{#ifeq:{{{action|}}}|shortlog
  |&lt;span style="display:none"&gt;[[Template:Git file/shortlog]]&lt;/span&gt;}}&lt;noinclude&gt;
{{doc}}
&lt;small&gt;Maintenance:
[[Special:WhatLinksHere/Template:Git file/blob_plain|blob_plain]],
[[Special:WhatLinksHere/Template:Git file/shortlog|shortlog]], [[Module:Callsigns]]&lt;/small&gt;
{{Category|External link templates}}
&lt;/noinclude&gt;</text>
    <sha1>b0dd60785ecfc4c10e0eb44572e4c4715689faf3</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Module:Callsigns</title>
  <ns>0</ns>
  <id>94</id>
  <revision>
    <id>232</id>
    <timestamp>2016-01-06T06:38:47Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "["mediawiki/extensions/AJAXPoll"] = "EAJP"; ["mediawiki/extensions/APC"] = "EAPC"; ["mediawiki/extensions/CirrusSearch"] = "ECIR"; ["mediawiki/extensions/SphinxSearch"] = "ESP..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="55405" xml:space="preserve">["mediawiki/extensions/AJAXPoll"] = "EAJP";
["mediawiki/extensions/APC"] = "EAPC";
["mediawiki/extensions/CirrusSearch"] = "ECIR";
["mediawiki/extensions/SphinxSearch"] = "ESPH";
["mediawiki/extensions/AWS"] = "EAWS";
["mediawiki/extensions/AWSSDK"] = "EAWK";
["mediawiki/extensions/AbsenteeLandlord"] = "EABL";
["mediawiki/extensions/AbuseFilter"] = "EABF";
["mediawiki/extensions/AccessControl"] = "EACC";
["mediawiki/extensions/AccountAudit"] = "EAAU";
["mediawiki/extensions/AccountInfo"] = "EAIN";
["mediawiki/extensions/ActionEditSubmit"] = "EAES";
["mediawiki/extensions/ActiveAbstract"] = "EAAB";
["mediawiki/extensions/ActivityMonitor"] = "EACM";
["mediawiki/extensions/AdManager"] = "EADM";
["mediawiki/extensions/AddMessages"] = "EAMS";
["mediawiki/extensions/AddThis"] = "EADT";
["mediawiki/extensions/AdminLinks"] = "EADL";
["mediawiki/extensions/Ads"] = "EADS";
["mediawiki/extensions/AdvancedMeta"] = "EAME";
["mediawiki/extensions/Agora"] = "EAGO";
["mediawiki/extensions/AjaxLogin"] = "EAJL";
["mediawiki/extensions/AkismetKlik"] = "EAKI";
["mediawiki/extensions/AllTimeZones"] = "EATZ";
["mediawiki/extensions/AnchorHandler"] = "EAHA";
["mediawiki/extensions/Annotator"] = "EANN";
["mediawiki/extensions/AntiBot"] = "EANB";
["mediawiki/extensions/AntiSpoof"] = "EANS";
["mediawiki/extensions/ApiExplorer"] = "EAPX";
["mediawiki/extensions/ApiSVGProxy"] = "EASP";
["mediawiki/extensions/ApiSandbox"] = "ESBX";
["mediawiki/extensions/ApprovedRevs"] = "EARE";
["mediawiki/extensions/Arrays"] = "EARR";
["mediawiki/extensions/ArticleCreationWorkflow"] = "EACW";
["mediawiki/extensions/ArticleFeedback"] = "EAFB";
["mediawiki/extensions/ArticleFeedbackv5"] = "EAFF";
["mediawiki/extensions/ArticleIndex"] = "EAID";
["mediawiki/extensions/AssertEdit"] = "EASE";
["mediawiki/extensions/Auth_remoteuser"] = "EARU";
["mediawiki/extensions/AuthorProtect"] = "EAUP";
["mediawiki/extensions/AutoCreateCategoryPages"] = "EACP";
["mediawiki/extensions/AutoProxyBlock"] = "EAPB";
["mediawiki/extensions/AutomaticBoardWelcome"] = "EABW";
["mediawiki/extensions/Awesomeness"] = "EAWE";
["mediawiki/extensions/AzharAuth"] = "EAZA";
["mediawiki/extensions/Babel"] = "EBAB";
["mediawiki/extensions/BatchUserRights"] = "EBUR";
["mediawiki/extensions/BayesianFilter"] = "EBAF";
["mediawiki/extensions/BetaFeatures"] = "EBET";
["mediawiki/extensions/BibManager"] = "EBIB";
["mediawiki/extensions/BiblioPlus"] = "EBPL";
["mediawiki/extensions/Blackout"] = "EBLA";
["mediawiki/extensions/BlameMaps"] = "EBLM";
["mediawiki/extensions/BlockAndNuke"] = "EBAN";
["mediawiki/extensions/BlogPage"] = "EBLO";
["mediawiki/extensions/BlueSpiceExtensions"] = "EBSE";
["mediawiki/extensions/BlueSpiceFoundation"] = "EBSF";
["mediawiki/extensions/BookManager"] = "EBMA";
["mediawiki/extensions/BookManagerv2"] = "EBMB";
["mediawiki/extensions/Bootstrap"] = "EBOO";
["mediawiki/extensions/BounceHandler"] = "EBHA";
["mediawiki/extensions/BreadCrumbs"] = "EBCR";
["mediawiki/extensions/BreadCrumbs2"] = "EBCS";
["mediawiki/extensions/CSS"] = "ECSS";
["mediawiki/extensions/Calendar"] = "ECAL";
["mediawiki/extensions/Campaigns"] = "ECAM";
["mediawiki/extensions/Capiunto"] = "ECAP";
["mediawiki/extensions/Carp"] = "ECAR";
["mediawiki/extensions/CategorySlideShow"] = "ECAS";
["mediawiki/extensions/CategorySortHeaders"] = "ECSH";
["mediawiki/extensions/CategoryTagSorter"] = "ECTS";
["mediawiki/extensions/CategoryTests"] = "ECTE";
["mediawiki/extensions/CategoryTree"] = "ECTR";
["mediawiki/extensions/CentralAuth"] = "ECAU";
["mediawiki/extensions/CentralLogging"] = "ECLO";
["mediawiki/extensions/CentralNotice"] = "ECNO";
["mediawiki/extensions/CentralNotice-BannerProxy"] = "ECNB";
["mediawiki/extensions/Challenge"] = "ECHA";
["mediawiki/extensions/CharInsert"] = "ECHI";
["mediawiki/extensions/CharRangeSpan"] = "ECRS";
["mediawiki/extensions/CheckUser"] = "ECHU";
["mediawiki/extensions/Checkpoint"] = "ECHE";
["mediawiki/extensions/Cite"] = "ECIT";
["mediawiki/extensions/CiteThisPage"] = "ECTP";
["mediawiki/extensions/Citoid"] = "ECEX";
["mediawiki/extensions/CleanChanges"] = "ECLC";
["mediawiki/extensions/ClickTracking"] = "ECLT";
["mediawiki/extensions/ClientSide"] = "ECLS";
["mediawiki/extensions/CloseWikis"] = "ECLW";
["mediawiki/extensions/CodeEditor"] = "ECED";
["mediawiki/extensions/CodeMirror"] = "ECMI";
["mediawiki/extensions/CodeReview"] = "ECRE";
["mediawiki/extensions/Collection"] = "ECOL";
["mediawiki/extensions/OfflineContentGenerator-service"] = "EOCS";
["mediawiki/extensions/OfflineContentGenerator-bundler"] = "EOCB";
["mediawiki/extensions/OfflineContentGenerator-html_renderer"] = "EOCH";
["mediawiki/extensions/OfflineContentGenerator-latex_renderer"] = "EOCL";
["mediawiki/extensions/OfflineContentGenerator-node_modules"] = "EOCN";
["mediawiki/extensions/OfflineContentGenerator-text_renderer"] = "EOCT";
["mediawiki/extensions/OfflineContentGenerator-zim_renderer"] = "EOCZ";
["mediawiki/extensions/CommentPages"] = "ECMP";
["mediawiki/extensions/Commentbox"] = "ECMB";
["mediawiki/extensions/Comments"] = "ECMT";
["mediawiki/extensions/CommonMessages"] = "ECMM";
["mediawiki/extensions/CommonsMetadata"] = "ECMD";
["mediawiki/extensions/CommunityApplications"] = "ECOA";
["mediawiki/extensions/CommunityHiring"] = "ECOH";
["mediawiki/extensions/CommunityTwitter"] = "ECOT";
["mediawiki/extensions/CommunityVoice"] = "ECOV";
["mediawiki/extensions/ConditionalShowSection"] = "ECON";
["mediawiki/extensions/Configure"] = "ECFG";
["mediawiki/extensions/ConfirmAccount"] = "ECAC";
["mediawiki/extensions/ConfirmEdit"] = "ECOE";
["mediawiki/extensions/CongressLookup"] = "ECLP";
["mediawiki/extensions/ContactPage"] = "ECPA";
["mediawiki/extensions/ContactPageFundraiser"] = "ECPF";
["mediawiki/extensions/ContentTranslation"] = "ECTX";
["mediawiki/extensions/Contest"] = "ECST";
["mediawiki/extensions/ContributionReporting"] = "ECNR";
["mediawiki/extensions/ContributionScores"] = "ECNS";
["mediawiki/extensions/ContributionTracking"] = "ECNT";
["mediawiki/extensions/Contributors"] = "ECNN";
["mediawiki/extensions/Convention"] = "ECOX";
["mediawiki/extensions/Convert2Wiki"] = "ECTW";
["mediawiki/extensions/CopyToClipboard"] = "ECTC";
["mediawiki/extensions/CreatePage"] = "ECRP";
["mediawiki/extensions/CreateRedirect"] = "ECRR";
["mediawiki/extensions/CreditTab"] = "ECTA";
["mediawiki/extensions/CreditsSource"] = "ECSO";
["mediawiki/extensions/CryoKey"] = "ECRK";
["mediawiki/extensions/CustomData"] = "ECUD";
["mediawiki/extensions/CustomUserSignup"] = "ECUS";
["mediawiki/extensions/DPLforum"] = "EDPF";
["mediawiki/extensions/DataTransfer"] = "EDTR";
["mediawiki/extensions/DataTypes"] = "EDTY";
["mediawiki/extensions/DebugMode"] = "EDBG";
["mediawiki/extensions/DeleteBatch"] = "EDBA";
["mediawiki/extensions/DeleteOwn"] = "EDOW";
["mediawiki/extensions/Description2"] = "EDES";
["mediawiki/extensions/DetectLanguage"] = "EDLA";
["mediawiki/extensions/DeviceMapLogCapture"] = "EDML";
["mediawiki/extensions/Diagnosis"] = "EDIA";
["mediawiki/extensions/Dice"] = "EDIE";
["mediawiki/extensions/DidYouKnow"] = "EDYK";
["mediawiki/extensions/DidYouMean"] = "EDYM";
["mediawiki/extensions/DisableAccount"] = "EDAC";
["mediawiki/extensions/Disambiguator"] = "EDIS";
["mediawiki/extensions/DiscussionThreading"] = "EDTH";
["mediawiki/extensions/DismissableSiteNotice"] = "EDSN";
["mediawiki/extensions/DisqusTag"] = "EDQT";
["mediawiki/extensions/DjangoAnalytics"] = "EDJA";
["mediawiki/extensions/DonationInterface"] = "EDOI";
["mediawiki/extensions/DoubleWiki"] = "EDWI";
["mediawiki/extensions/DownloadCounter"] = "EDCO";
["mediawiki/extensions/Drafts"] = "EDRA";
["mediawiki/extensions/DumpHTML"] = "EDHT";
["mediawiki/extensions/Duplicator"] = "EDUP";
["mediawiki/extensions/DynamicPageList"] = "EDPL";
["mediawiki/extensions/DynamicSidebar"] = "EDSB";
["mediawiki/extensions/E3Experiments"] = "EEEE";
["mediawiki/extensions/Echo"] = "ECHO";
["mediawiki/extensions/EditPageTracking"] = "EEPT";
["mediawiki/extensions/EditSimilar"] = "EESI";
["mediawiki/extensions/EditSubpages"] = "EESP";
["mediawiki/extensions/Editcount"] = "EECT";
["mediawiki/extensions/EducationProgram"] = "EEDU";
["mediawiki/extensions/Elastica"] = "EELA";
["mediawiki/extensions/EmailCapture"] = "EMCP";
["mediawiki/extensions/EnhanceContactForm"] = "EECF";
["mediawiki/extensions/ErrorHandler"] = "EERR";
["mediawiki/extensions/EtherEditor"] = "EETH";
["mediawiki/extensions/EtherpadLite"] = "EEPL";
["mediawiki/extensions/EventLogging"] = "EEVL";
["mediawiki/extensions/ExpandTemplates"] = "EETE";
["mediawiki/extensions/ExtTab"] = "EEXT";
["mediawiki/extensions/ExtensionDistributor"] = "EXDI";
["mediawiki/extensions/ExternalArticles"] = "EXAR";
["mediawiki/extensions/ExternalData"] = "EXDA";
["mediawiki/extensions/ExtraLanguageLink"] = "EXLL";
["mediawiki/extensions/FanBoxes"] = "EFAN";
["mediawiki/extensions/FeaturedFeeds"] = "EFFD";
["mediawiki/extensions/FeedsFromPrivateWikis"] = "EFFP";
["mediawiki/extensions/FilterListUsers"] = "EFLU";
["mediawiki/extensions/FirstSteps"] = "EFIR";
["mediawiki/extensions/FixedHeaderTable"] = "EFHT";
["mediawiki/extensions/FlaggedRevs"] = "EFLR";
["mediawiki/extensions/Flow"] = "EFLW";
["mediawiki/extensions/FlvHandler"] = "EFLV";
["mediawiki/extensions/ForcePreview"] = "EFOP";
["mediawiki/extensions/FormPreloadPostCache"] = "EFPP";
["mediawiki/extensions/FormatDates"] = "EFOD";
["mediawiki/extensions/FormatNum"] = "EFON";
["mediawiki/extensions/FormelApplet"] = "EFAP";
["mediawiki/extensions/Foxway"] = "EFOX";
["mediawiki/extensions/FundraiserLandingPage"] = "EFUL";
["mediawiki/extensions/FundraisingChart"] = "EFCH";
["mediawiki/extensions/FundraisingEmailUnsubscribe"] = "EFEU";
["mediawiki/extensions/FundraisingTranslateWorkflow"] = "EFTW";
["mediawiki/extensions/GWToolset"] = "EGWT";
["mediawiki/extensions/Gadgets"] = "EGAD";
["mediawiki/extensions/Genderize"] = "EGEN";
["mediawiki/extensions/GeoCrumbs"] = "EGCR";
["mediawiki/extensions/GeoData"] = "EGDA";
["mediawiki/extensions/GeoGebra"] = "EGGE";
["mediawiki/extensions/GettingStarted"] = "EGST";
["mediawiki/extensions/Git2Pages"] = "EGTP";
["mediawiki/extensions/Gitweb"] = "EGWE";
["mediawiki/extensions/GlobalBlocking"] = "EGBL";
["mediawiki/extensions/GlobalContributions"] = "EGCO";
["mediawiki/extensions/GlobalCssJs"] = "EGCJ";
["mediawiki/extensions/GlobalNotice"] = "EGNO";
["mediawiki/extensions/GlobalPreferences"] = "EGPR";
["mediawiki/extensions/GlobalUsage"] = "EGUS";
["mediawiki/extensions/GlobalUserGroups"] = "EGUG";
["mediawiki/extensions/GlobalUserPage"] = "EGUP";
["mediawiki/extensions/GlobalUserrights"] = "EGUR";
["mediawiki/extensions/GoToShell"] = "EGTS";
["mediawiki/extensions/GoogleAdSense"] = "EGAS";
["mediawiki/extensions/GoogleAppEngine"] = "EGAE";
["mediawiki/extensions/GoogleCustomWikiSearch"] = "EGCW";
["mediawiki/extensions/GoogleDocTag"] = "EGDT";
["mediawiki/extensions/GoogleDocs4MW"] = "EGDM";
["mediawiki/extensions/GoogleLogin"] = "EGLO";
["mediawiki/extensions/GoogleMaps"] = "EGMA";
["mediawiki/extensions/GoogleNewsSitemap"] = "EGNS";
["mediawiki/extensions/GooglePlusOne"] = "EGPO";
["mediawiki/extensions/GoogleSiteSearch"] = "EGSS";
["mediawiki/extensions/Graph"] = "EGRA";
["mediawiki/extensions/GraphViz"] = "EGVI";
["mediawiki/extensions/GroupsSidebar"] = "EGSB";
["mediawiki/extensions/GuidedTour"] = "EGTO";
["mediawiki/extensions/GuidedTour-guiders"] = "EGTG";
["mediawiki/extensions/HSTS"] = "EHST";
["mediawiki/extensions/HTMLTags"] = "EHTT";
["mediawiki/extensions/HTMLets"] = "EHTL";
["mediawiki/extensions/HashTables"] = "EHAT";
["mediawiki/extensions/HeaderTabs"] = "EHET";
["mediawiki/extensions/HelpCommons"] = "EHCO";
["mediawiki/extensions/HelpPages"] = "EHPA";
["mediawiki/extensions/HidePrefix"] = "EHPR";
["mediawiki/extensions/HierarchyBuilder"] = "EHIB";
["mediawiki/extensions/HostStats"] = "EHOS";
["mediawiki/extensions/Hovergallery"] = "EHOV";
["mediawiki/extensions/I18nTags"] = "EINT";
["mediawiki/extensions/IfTemplates"] = "EIFT";
["mediawiki/extensions/IframePage"] = "EIFP";
["mediawiki/extensions/ImageLink"] = "EILI";
["mediawiki/extensions/ImageMap"] = "EIMA";
["mediawiki/extensions/ImageMetrics"] = "EIME";
["mediawiki/extensions/ImageTagging"] = "EIMT";
["mediawiki/extensions/IndexFunction"] = "EINF";
["mediawiki/extensions/InlineCategorizer"] = "EINC";
["mediawiki/extensions/InputBox"] = "EINB";
["mediawiki/extensions/Insider"] = "EINS";
["mediawiki/extensions/InteractiveBlockMessage"] = "EIBM";
["mediawiki/extensions/Interlanguage"] = "EILA";
["mediawiki/extensions/Interwiki"] = "EIWA";
["mediawiki/extensions/InterwikiIntegration"] = "EIWI";
["mediawiki/extensions/InterwikiMagic"] = "EIWM";
["mediawiki/extensions/InterwikiMap"] = "EIWN";
["mediawiki/extensions/InviteSignup"] = "EIVS";
["mediawiki/extensions/IssueTracker"] = "EIST";
["mediawiki/extensions/JSBreadCrumbs"] = "EJSB";
["mediawiki/extensions/Josa"] = "EJOS";
["mediawiki/extensions/JsonConfig"] = "EJSC";
["mediawiki/extensions/JsonData"] = "EJSD";
["mediawiki/extensions/JsonData-JsonSchema"] = "EJSS";
["mediawiki/extensions/LabeledSectionTransclusion"] = "ELST";
["mediawiki/extensions/LandingCheck"] = "ELCH";
["mediawiki/extensions/LanguageSelector"] = "ELSR";
["mediawiki/extensions/LanguageTag"] = "ELTA";
["mediawiki/extensions/LastModified"] = "ELMO";
["mediawiki/extensions/LdapAuthentication"] = "ELDA";
["mediawiki/extensions/Less"] = "ELES";
["mediawiki/extensions/LifeWeb"] = "ELWE";
["mediawiki/extensions/LifeWebCore"] = "ELWC";
["mediawiki/extensions/LightweightRDFa"] = "ELRA";
["mediawiki/extensions/Limn"] = "ELIM";
["mediawiki/extensions/Lingo"] = "ELIN";
["mediawiki/extensions/LinkFilter"] = "ELIF";
["mediawiki/extensions/LinkSuggest"] = "ELIS";
["mediawiki/extensions/LinkedWiki"] = "ELIW";
["mediawiki/extensions/LiquidThreads"] = "ELQT";
["mediawiki/extensions/ListSignup"] = "ELSS";
["mediawiki/extensions/Listings"] = "ELSG";
["mediawiki/extensions/LiveTranslate"] = "ELIT";
["mediawiki/extensions/LocalisationUpdate"] = "ELOC";
["mediawiki/extensions/LockDownEnglishPages"] = "ELDE";
["mediawiki/extensions/Lockdown"] = "ELCK";
["mediawiki/extensions/LogEntry"] = "ELGE";
["mediawiki/extensions/LogoFunctions"] = "ELOG";
["mediawiki/extensions/LookupUser"] = "ELOU";
["mediawiki/extensions/LoopFunctions"] = "ELOF";
["mediawiki/extensions/Loops"] = "ELOO";
["mediawiki/extensions/MSSQLBackCompat"] = "EMSQ";
["mediawiki/extensions/MWSearch"] = "EMWS";
["mediawiki/extensions/MagicNoCache"] = "EMNC";
["mediawiki/extensions/Maintenance"] = "EMAI";
["mediawiki/extensions/MaintenanceShell"] = "EMSH";
["mediawiki/extensions/Mantle"] = "EMAN";
["mediawiki/extensions/MapSources"] = "EMSO";
["mediawiki/extensions/Maps"] = "EMAP";
["mediawiki/extensions/MarkAsHelpful"] = "EMAH";
["mediawiki/extensions/MassEditRegex"] = "EMER";
["mediawiki/extensions/MassMessage"] = "EMAM";
["mediawiki/extensions/Math"] = "EMAT";
["mediawiki/extensions/MathSearch"] = "EMAS";
["mediawiki/extensions/MediaFunctions"] = "EMFU";
["mediawiki/extensions/MediaWikiAuth"] = "EMWA";
["mediawiki/extensions/MediaWikiChat"] = "EMWC";
["mediawiki/extensions/MiniInvite"] = "EMIV";
["mediawiki/extensions/Minifier"] = "EMIN";
["mediawiki/extensions/MixedNamespaceSearchSuggestions"] = "EMNS";
["mediawiki/extensions/MobileApp"] = "EMOB";
["mediawiki/extensions/MobileDetect"] = "EMDE";
["mediawiki/extensions/MobileFrontend"] = "EMFR";
["mediawiki/extensions/Model"] = "EMOD";
["mediawiki/extensions/MolHandler"] = "EMOL";
["mediawiki/extensions/MoodBar"] = "EMOO";
["mediawiki/extensions/Moodle"] = "EMDL";
["mediawiki/extensions/Mpdf"] = "EMPD";
["mediawiki/extensions/MsLinks"] = "EMSL";
["mediawiki/extensions/MsUpload"] = "EMSU";
["mediawiki/extensions/MultiMaps"] = "EMMA";
["mediawiki/extensions/MultiUpload"] = "EMUP";
["mediawiki/extensions/MultimediaPlayer"] = "EMMP";
["mediawiki/extensions/MultimediaViewer"] = "EMMV";
["mediawiki/extensions/MwEmbedSupport"] = "EMES";
["mediawiki/extensions/MyVariables"] = "EMYV";
["mediawiki/extensions/NSFileRepo"] = "ENSF";
["mediawiki/extensions/NamespaceHTML"] = "ENSH";
["mediawiki/extensions/NamespacePaths"] = "ENSP";
["mediawiki/extensions/NamespaceRelations"] = "ENSR";
["mediawiki/extensions/Narayam"] = "ENAR";
["mediawiki/extensions/NaturalLanguageList"] = "ENLL";
["mediawiki/extensions/NavigationTiming"] = "ENTI";
["mediawiki/extensions/Negref"] = "ENEG";
["mediawiki/extensions/NetworkAuth"] = "ENAU";
["mediawiki/extensions/NewSignupPage"] = "ENSU";
["mediawiki/extensions/NewUserMessage"] = "ENUM";
["mediawiki/extensions/NewUserNotif"] = "ENUN";
["mediawiki/extensions/NewUsersList"] = "ENUL";
["mediawiki/extensions/NewestPages"] = "ENWP";
["mediawiki/extensions/News"] = "ENEW";
["mediawiki/extensions/NewsBox"] = "ENBX";
["mediawiki/extensions/Newsletter"] = "ENLT";
["mediawiki/extensions/NoTitle"] = "ENOT";
["mediawiki/extensions/Nonlinear"] = "ENOL";
["mediawiki/extensions/Nostalgia"] = "ENOS";
["mediawiki/extensions/Nuke"] = "ENUK";
["mediawiki/extensions/NukeDPL"] = "ENUD";
["mediawiki/extensions/NumberFormat"] = "ENFM";
["mediawiki/extensions/NumberOfWikis"] = "ENOW";
["mediawiki/extensions/Numbertext"] = "ENUT";
["mediawiki/extensions/NumerAlpha"] = "ENUA";
["mediawiki/extensions/OAI"] = "EOAI";
["mediawiki/extensions/OATHAuth"] = "EOAT";
["mediawiki/extensions/OAuth"] = "EOAU";
["mediawiki/extensions/OAuthAuthentication"] = "EOAA";
["mediawiki/extensions/OdbcDatabase"] = "EODB";
["mediawiki/extensions/Offline"] = "EOFF";
["mediawiki/extensions/OfflineImportLexicon"] = "EOIL";
["mediawiki/extensions/OggHandler"] = "EOGG";
["mediawiki/extensions/OnlineStatus"] = "EOSS";
["mediawiki/extensions/OnlineStatusBar"] = "EOSB";
["mediawiki/extensions/OnlyRecentRecentChanges"] = "EORR";
["mediawiki/extensions/OpenBadges"] = "EOBA";
["mediawiki/extensions/OpenGraphMeta"] = "EOGM";
["mediawiki/extensions/OpenID"] = "EOID";
["mediawiki/extensions/OpenSearchXml"] = "EOSX";
["mediawiki/extensions/OpenStackManager"] = "EOST";
["mediawiki/extensions/OpenStreetMapSlippyMap"] = "EOSM";
["mediawiki/extensions/OracleTextSearch"] = "EOTS";
["mediawiki/extensions/Oversight"] = "EOVS";
["mediawiki/extensions/PGFTikZ"] = "ETKZ";
["mediawiki/extensions/PHPExcel"] = "EXCL";
["mediawiki/extensions/PageBlock"] = "EPBL";
["mediawiki/extensions/PageCreationNotif"] = "EPCN";
["mediawiki/extensions/PageDisqus"] = "EPDQ";
["mediawiki/extensions/PageImages"] = "EPIM";
["mediawiki/extensions/PageInCat"] = "EPIC";
["mediawiki/extensions/PageLanguage"] = "EPLA";
["mediawiki/extensions/PageNotice"] = "EPNO";
["mediawiki/extensions/PageSchemas"] = "EPSC";
["mediawiki/extensions/PageTools"] = "EPTO";
["mediawiki/extensions/PageTriage"] = "EPTR";
["mediawiki/extensions/PagedTiffHandler"] = "EPTH";
["mediawiki/extensions/PanScroll"] = "EPAN";
["mediawiki/extensions/ParserFun"] = "EPFU";
["mediawiki/extensions/ParserFunctions"] = "EPFN";
["mediawiki/extensions/ParserHooks"] = "EPHO";
["mediawiki/extensions/Parsoid"] = "EPAR";
["mediawiki/extensions/Parsoid-cpp-contrib-libhubbub"] = "EPAH";
["mediawiki/extensions/Parsoid-cpp-contrib-pugixml"] = "EPAP";
["mediawiki/extensions/Parsoid-js-contrib"] = "EPJS";
["mediawiki/extensions/PdfBook"] = "EPBO";
["mediawiki/extensions/PdfExport"] = "EPEX";
["mediawiki/extensions/PdfHandler"] = "EPHD";
["mediawiki/extensions/PerPageLicense"] = "EPPL";
["mediawiki/extensions/Persona"] = "EPER";
["mediawiki/extensions/Petition"] = "EPET";
["mediawiki/extensions/Phalanx"] = "EPHA";
["mediawiki/extensions/PhpHighlight"] = "EPHI";
["mediawiki/extensions/PhpTags"] = "ETAG";
["mediawiki/extensions/PhpTagsDebugger"] = "ETDE";
["mediawiki/extensions/PhpTagsFunctions"] = "ETFU";
["mediawiki/extensions/PhpTagsMaps"] = "ETMA";
["mediawiki/extensions/PhpTagsSMW"] = "ETSM";
["mediawiki/extensions/PhpTagsWidgets"] = "ETWD";
["mediawiki/extensions/PhpTagsWiki"] = "ETWK";
["mediawiki/extensions/PictureGame"] = "EPGA";
["mediawiki/extensions/Poem"] = "EPOE";
["mediawiki/extensions/Poll"] = "EPOL";
["mediawiki/extensions/PollNY"] = "EPNY";
["mediawiki/extensions/Polyglot"] = "EPGT";
["mediawiki/extensions/PoolCounter"] = "EPOC";
["mediawiki/extensions/PopupPages"] = "EPPP";
["mediawiki/extensions/Popups"] = "EPOP";
["mediawiki/extensions/PostEdit"] = "EPOS";
["mediawiki/extensions/PrefStats"] = "EPST";
["mediawiki/extensions/PrefSwitch"] = "EPSW";
["mediawiki/extensions/Premoderation"] = "EPRM";
["mediawiki/extensions/PrivateDomains"] = "EPRD";
["mediawiki/extensions/PronunciationRecording"] = "EPRR";
["mediawiki/extensions/ProofreadPage"] = "EPRP";
["mediawiki/extensions/ProtectSite"] = "EPRO";
["mediawiki/extensions/ProxyListDb"] = "EPLD";
["mediawiki/extensions/PubSubHubbub"] = "EPSH";
["mediawiki/extensions/PureWikiDeletion"] = "EPWD";
["mediawiki/extensions/PurgeClickThrough"] = "EPCT";
["mediawiki/extensions/Push"] = "EPUS";
["mediawiki/extensions/PushToWatch"] = "EPTW";
["mediawiki/extensions/Quantcast"] = "EQCS";
["mediawiki/extensions/QuickResponse"] = "EQRS";
["mediawiki/extensions/Quiz"] = "EQUI";
["mediawiki/extensions/QuizGame"] = "EQGA";
["mediawiki/extensions/QuizTabulate"] = "EQTA";
["mediawiki/extensions/RDFIO"] = "ERDF";
["mediawiki/extensions/RPED"] = "ERPE";
["mediawiki/extensions/RSS"] = "ERSS";
["mediawiki/extensions/RT"] = "ERQT";
["mediawiki/extensions/RandomFeaturedUser"] = "ERFU";
["mediawiki/extensions/RandomGameUnit"] = "ERGU";
["mediawiki/extensions/RandomImage"] = "ERIM";
["mediawiki/extensions/RandomImageByCategory"] = "ERIC";
["mediawiki/extensions/RandomInCategory"] = "ERAC";
["mediawiki/extensions/RandomRootPage"] = "ERRP";
["mediawiki/extensions/RandomUsersWithAvatars"] = "ERUA";
["mediawiki/extensions/Ratings"] = "ERAT";
["mediawiki/extensions/ReaderFeedback"] = "ERFE";
["mediawiki/extensions/ReassignEdits"] = "ERAE";
["mediawiki/extensions/RecentActivityFeed"] = "ERAF";
["mediawiki/extensions/RefreshSpecial"] = "ERES";
["mediawiki/extensions/RegexFun"] = "ERXU";
["mediawiki/extensions/RegexFunctions"] = "ERXF";
["mediawiki/extensions/RelatedArticles"] = "ERAR";
["mediawiki/extensions/RelatedSites"] = "ERSI";
["mediawiki/extensions/RelationLinks"] = "ERLI";
["mediawiki/extensions/Renameuser"] = "EREN";
["mediawiki/extensions/ReorderParserPhases"] = "ERPP";
["mediawiki/extensions/ReplaceSet"] = "ERPS";
["mediawiki/extensions/ReplaceText"] = "ERPT";
["mediawiki/extensions/RevisionCommentSupplement"] = "ERCS";
["mediawiki/extensions/RightFunctions"] = "ERIF";
["mediawiki/extensions/SSLClientAuthentication"] = "ESCA";
["mediawiki/extensions/SVGEdit"] = "ESVE";
["mediawiki/extensions/SacredText"] = "ESAT";
["mediawiki/extensions/SandboxLink"] = "ESAL";
["mediawiki/extensions/Sarcasm"] = "ESAR";
["mediawiki/extensions/ScanSet"] = "ESST";
["mediawiki/extensions/Score"] = "ESCR";
["mediawiki/extensions/Screenplay"] = "ESCP";
["mediawiki/extensions/Scribunto"] = "ELUA";
["mediawiki/extensions/SearchExtraNS"] = "ESEN";
["mediawiki/extensions/SearchRealnames"] = "ESRE";
["mediawiki/extensions/SectionDisqus"] = "ESDQ";
["mediawiki/extensions/SecureHTML"] = "ESHT";
["mediawiki/extensions/SecurePasswords"] = "ESPW";
["mediawiki/extensions/SecurePoll"] = "ESPO";
["mediawiki/extensions/SecureSessions"] = "ESSE";
["mediawiki/extensions/SelectCategory"] = "ESLC";
["mediawiki/extensions/SelectTag"] = "ESLT";
["mediawiki/extensions/SemanticACL"] = "ESAC";
["mediawiki/extensions/SemanticBundle"] = "ESBU";
["mediawiki/extensions/SemanticComments"] = "ESCO";
["mediawiki/extensions/SemanticCompoundQueries"] = "ESCQ";
["mediawiki/extensions/SemanticDrilldown"] = "ESDD";
["mediawiki/extensions/SemanticDummyEditor"] = "ESDE";
["mediawiki/extensions/SemanticExpressiveness"] = "ESEX";
["mediawiki/extensions/SemanticExtraSpecialProperties"] = "ESES";
["mediawiki/extensions/SemanticForms"] = "ESFO";
["mediawiki/extensions/SemanticFormsInputs"] = "ESFI";
["mediawiki/extensions/SemanticGenealogy"] = "ESGE";
["mediawiki/extensions/SemanticGlossary"] = "ESGL";
["mediawiki/extensions/SemanticHighcharts"] = "ESHI";
["mediawiki/extensions/SemanticImageAnnotator"] = "ESIA";
["mediawiki/extensions/SemanticImageInput"] = "ESII";
["mediawiki/extensions/SemanticInternalObjects"] = "ESIO";
["mediawiki/extensions/SemanticMaps"] = "ESMA";
["mediawiki/extensions/SemanticMediaWiki"] = "ESMW";
["mediawiki/extensions/SemanticPageMaker"] = "ESPM";
["mediawiki/extensions/SemanticPageSeries"] = "ESPS";
["mediawiki/extensions/SemanticRating"] = "ESRA";
["mediawiki/extensions/SemanticResultFormats"] = "ESRF";
["mediawiki/extensions/SemanticSifter"] = "ESSI";
["mediawiki/extensions/SemanticSignup"] = "ESSU";
["mediawiki/extensions/SemanticTasks"] = "ESTA";
["mediawiki/extensions/SemanticTitle"] = "ESTI";
["mediawiki/extensions/SemanticUpdateOnPurge"] = "ESUP";
["mediawiki/extensions/SemanticWatchlist"] = "ESWL";
["mediawiki/extensions/SemanticWebBrowser"] = "ESWB";
["mediawiki/extensions/SharedCssJs"] = "ESCJ";
["mediawiki/extensions/ShortUrl"] = "ESUR";
["mediawiki/extensions/ShortUrlApi"] = "ESUA";
["mediawiki/extensions/ShoutBox"] = "ESBO";
["mediawiki/extensions/ShoutWikiAds"] = "ESWA";
["mediawiki/extensions/SideBarMenu"] = "ESBM";
["mediawiki/extensions/SidebarDonateBox"] = "ESDB";
["mediawiki/extensions/SignWritingMediaWikiPlugin"] = "ESWP";
["mediawiki/extensions/SimpleAntiSpam"] = "ESAS";
["mediawiki/extensions/SimpleChanges"] = "ESCH";
["mediawiki/extensions/SimpleFarm"] = "ESFA";
["mediawiki/extensions/SimpleSecurity"] = "ESSC";
["mediawiki/extensions/SimpleSurvey"] = "ESIS";
["mediawiki/extensions/SiteMatrix"] = "ESMX";
["mediawiki/extensions/SiteMetrics"] = "ESMT";
["mediawiki/extensions/SiteScout"] = "ESCT";
["mediawiki/extensions/SiteSettings"] = "ESET";
["mediawiki/extensions/SkelJS"] = "ESJS";
["mediawiki/extensions/SkinPerNamespace"] = "ESPN";
["mediawiki/extensions/SkinPerPage"] = "ESPP";
["mediawiki/extensions/SlimboxThumbs"] = "ESBT";
["mediawiki/extensions/SmoothGallery"] = "ESMG";
["mediawiki/extensions/SocialLogin"] = "ESLI";
["mediawiki/extensions/SocialProfile"] = "ESPR";
["mediawiki/extensions/SoftwareVersion"] = "ESVN";
["mediawiki/extensions/Solarium"] = "ESLA";
["mediawiki/extensions/SolrStore"] = "ESOS";
["mediawiki/extensions/SoundManager2Button"] = "ESMB";
["mediawiki/extensions/SpamBlacklist"] = "ESPB";
["mediawiki/extensions/Spark"] = "ESPK";
["mediawiki/extensions/Special404"] = "ESPF";
["mediawiki/extensions/SpecialNamespaces"] = "ESNS";
["mediawiki/extensions/SpellingApi"] = "ESPA";
["mediawiki/extensions/SportsTeams"] = "ESPT";
["mediawiki/extensions/Spreadsheet"] = "ESSH";
["mediawiki/extensions/StaffEdits"] = "ESTE";
["mediawiki/extensions/StalkerLog"] = "ESTL";
["mediawiki/extensions/StarterWiki"] = "ESTW";
["mediawiki/extensions/StickToThatLanguage"] = "ESTT";
["mediawiki/extensions/StopForumSpam"] = "ESFS";
["mediawiki/extensions/StrategyWiki"] = "ESTR";
["mediawiki/extensions/StringFunctionsEscaped"] = "ESFE";
["mediawiki/extensions/SubPageList"] = "ESPL";
["mediawiki/extensions/SubPageList3"] = "ESPC";
["mediawiki/extensions/SubpageFun"] = "ESFN";
["mediawiki/extensions/SubpageSortkey"] = "ESSK";
["mediawiki/extensions/Sudo"] = "ESUD";
["mediawiki/extensions/Suhosin"] = "ESUH";
["mediawiki/extensions/Survey"] = "ESUV";
["mediawiki/extensions/SwarmExport"] = "ESWX";
["mediawiki/extensions/SwiftCloudFiles"] = "ESCF";
["mediawiki/extensions/SwiftMailer"] = "ESWM";
["mediawiki/extensions/SyntaxHighlight_GeSHi"] = "ESHG";
["mediawiki/extensions/SyntaxHighlighter"] = "ESHL";
["mediawiki/extensions/Tabber"] = "ETBR";
["mediawiki/extensions/Tabs"] = "ETAB";
["mediawiki/extensions/Teahouse"] = "ETEA";
["mediawiki/extensions/TemplateData"] = "ETDA";
["mediawiki/extensions/TemplateInfo"] = "ETIN";
["mediawiki/extensions/TemplateSandbox"] = "ETSA";
["mediawiki/extensions/TextExtracts"] = "ETEX";
["mediawiki/extensions/Thanks"] = "ETHA";
["mediawiki/extensions/Theme"] = "ETHM";
["mediawiki/extensions/ThemeDesigner"] = "ETHD";
["mediawiki/extensions/ThrottleOverride"] = "ETHO";
["mediawiki/extensions/ThumbParser"] = "ETHP";
["mediawiki/extensions/TimeMachine"] = "ETIM";
["mediawiki/extensions/TimedMediaHandler"] = "ETMH";
["mediawiki/extensions/TimelineTable"] = "ETLT";
["mediawiki/extensions/TimezoneSelector"] = "ETZS";
["mediawiki/extensions/TitleBlacklist"] = "ETBL";
["mediawiki/extensions/TitleIcon"] = "ETIC";
["mediawiki/extensions/TitleKey"] = "ETIK";
["mediawiki/extensions/TocTree"] = "ETTR";
["mediawiki/extensions/Tooltip"] = "ETTI";
["mediawiki/extensions/TorBlock"] = "ETOR";
["mediawiki/extensions/Translate"] = "ETRA";
["mediawiki/extensions/TranslateSvg"] = "ETRS";
["mediawiki/extensions/TranslationNotifications"] = "ETRN";
["mediawiki/extensions/Transliterator"] = "ETRX";
["mediawiki/extensions/TrustedXFF"] = "ETXF";
["mediawiki/extensions/TweetANew"] = "ETAN";
["mediawiki/extensions/TwitterCards"] = "ETWC";
["mediawiki/extensions/TwitterLogin"] = "ETWL";
["mediawiki/extensions/TwnMainPage"] = "ETWN";
["mediawiki/extensions/TwoFactorAuthentication"] = "ETFA";
["mediawiki/extensions/UIFeedback"] = "EUIF";
["mediawiki/extensions/URNames"] = "EURN";
["mediawiki/extensions/UnicodeConverter"] = "EUCO";
["mediawiki/extensions/UnitTest"] = "EUTE";
["mediawiki/extensions/UniversalLanguageSelector"] = "EULS";
["mediawiki/extensions/UpdateMediaWiki"] = "EUMW";
["mediawiki/extensions/UploadBlacklist"] = "EUBL";
["mediawiki/extensions/UploadLocal"] = "EULO";
["mediawiki/extensions/UploadWizard"] = "EUWI";
["mediawiki/extensions/UrlGetParameters"] = "EUGP";
["mediawiki/extensions/UrlShortener"] = "EUSH";
["mediawiki/extensions/UserDailyContribs"] = "EUDC";
["mediawiki/extensions/UserFunctions"] = "EUFU";
["mediawiki/extensions/UserGroups"] = "EUGR";
["mediawiki/extensions/UserMerge"] = "EUME";
["mediawiki/extensions/UserOptionStats"] = "EUOS";
["mediawiki/extensions/UserPageViewTracker"] = "EUPV";
["mediawiki/extensions/UserStatus"] = "EUST";
["mediawiki/extensions/UserThrottle"] = "EUTH";
["mediawiki/extensions/VIKI"] = "EVIK";
["mediawiki/extensions/Validator"] = "EVAL";
["mediawiki/extensions/ValueView"] = "EVVI";
["mediawiki/extensions/Variables"] = "EVAR";
["mediawiki/extensions/Vector"] = "EVEC";
["mediawiki/extensions/BetaSandbox"] = "EBSA";
["mediawiki/extensions/Video"] = "EVID";
["mediawiki/extensions/VideoJsPlayer"] = "EVJS";
["mediawiki/extensions/ViewFiles"] = "EVFI";
["mediawiki/extensions/Views"] = "EVWS";
["mediawiki/extensions/Vine"] = "EVIN";
["mediawiki/extensions/VipsScaler"] = "EVIP";
["mediawiki/extensions/VisualChat"] = "EVCH";
["mediawiki/extensions/VisualEditor-MediaWiki"] = "EVED";
["mediawiki/extensions/VoteNY"] = "EVNY";
["mediawiki/extensions/WYSIWYG"] = "EWYS";
["mediawiki/extensions/WantedPagesFromNS"] = "EWPN";
["mediawiki/extensions/WatchSubpages"] = "EWSP";
["mediawiki/extensions/WebCache"] = "EWCA";
["mediawiki/extensions/WebChat"] = "EWCH";
["mediawiki/extensions/WebFonts"] = "EWBF";
["mediawiki/extensions/WebPlatformAuth"] = "EWPA";
["mediawiki/extensions/WebPlatformSearchAutocomplete"] = "EWPC";
["mediawiki/extensions/WhiteSpace"] = "EWHI";
["mediawiki/extensions/WhitelistPages"] = "EWHP";
["mediawiki/extensions/WhoIsWatching"] = "EWIW";
["mediawiki/extensions/Widgets"] = "EWID";
["mediawiki/extensions/WikEdDiff"] = "EWEF";
["mediawiki/extensions/WikiArticleFeeds"] = "EWAF";
["mediawiki/extensions/WikiCategoryTagCloud"] = "EWCT";
["mediawiki/extensions/WikiEditor"] = "EWED";
["mediawiki/extensions/WikiForum"] = "EWFO";
["mediawiki/extensions/WikiGrok"] = "EWGR";
["mediawiki/extensions/WikiLexicalData"] = "EWLD";
["mediawiki/extensions/WikiLove"] = "EWLO";
["mediawiki/extensions/WikiLovesMonuments"] = "EWLM";
["mediawiki/extensions/WikiObjectModel"] = "EWOM";
["mediawiki/extensions/WikiTextLoggedInOut"] = "EWLI";
["mediawiki/extensions/WikiTwidget"] = "EWTW";
["mediawiki/extensions/Wikibase"] = "EWBA";
["mediawiki/extensions/Wikibase-easyrdf"] = "EWBE";
["mediawiki/extensions/WikibaseClient"] = "EWBC";
["mediawiki/extensions/WikibaseLib"] = "EWBL";
["mediawiki/extensions/WikibaseMobile"] = "EWBM";
["mediawiki/extensions/WikibaseQuery"] = "EWBQ";
["mediawiki/extensions/WikibaseSolr"] = "EWBS";
["mediawiki/extensions/Wikidata"] = "EWDA";
["mediawiki/extensions/WikidataEntitySuggester"] = "EWDE";
["mediawiki/extensions/Wikilog"] = "EWLG";
["mediawiki/extensions/WikimediaEvents"] = "EWMV";
["mediawiki/extensions/WikimediaIncubator"] = "EWMI";
["mediawiki/extensions/WikimediaMaintenance"] = "EWMA";
["mediawiki/extensions/WikimediaMessages"] = "EWME";
["mediawiki/extensions/WikimediaShopLink"] = "EWSL";
["mediawiki/extensions/WikivoteMapsYandex"] = "EWMY";
["mediawiki/extensions/WindowsAzureSDK"] = "EWAK";
["mediawiki/extensions/WindowsAzureStorage"] = "EWAS";
["mediawiki/extensions/Workflow"] = "EWFL";
["mediawiki/extensions/XAnalytics"] = "EXAN";
["mediawiki/extensions/XMLContent"] = "EXCE";
["mediawiki/extensions/YetAnotherKeywords"] = "EYAK";
["mediawiki/extensions/YotpoReviews"] = "EYRE";
["mediawiki/extensions/YouTube"] = "EYTB";
["mediawiki/extensions/ZeroBanner"] = "EZBA";
["mediawiki/extensions/ZeroPortal"] = "EZPO";
["mediawiki/extensions/ZeroRatedMobileAccess"] = "EZRM";
["mediawiki/extensions/CLDR"] = "ECLD";
["mediawiki/extensions/examples"] = "EXAM";
["mediawiki/extensions/GoogleAnalytics"] = "EGAN";
["mediawiki/extensions/Intersection"] = "EAND";
["mediawiki/extensions/Timeline"] = "ETLN";
["mediawiki/extensions/Wikihiero"] = "EHIE";
["mediawiki/skins/BlueSky"] = "SBLS";
["mediawiki/skins/BlueSpiceSkin"] = "SBSS";
["mediawiki/skins/Bouquet"] = "SBOU";
["mediawiki/skins/CologneBlue"] = "SCBL";
["mediawiki/skins/Daddio"] = "SDAD";
["mediawiki/skins/DeskMessMirrored"] = "SDMM";
["mediawiki/skins/Donate"] = "SDON";
["mediawiki/skins/Dusk"] = "SDUS";
["mediawiki/skins/DuskToDawn"] = "SDTD";
["mediawiki/skins/Example"] = "SEXA";
["mediawiki/skins/Gamepress"] = "SGPR";
["mediawiki/skins/GreyStuff"] = "SGRY";
["mediawiki/skins/Mask"] = "SMSK";
["mediawiki/skins/Metrolook"] = "SMTL";
["mediawiki/skins/Modern"] = "SMOD";
["mediawiki/skins/MonoBook"] = "SMNB";
["mediawiki/skins/Nimbus"] = "SNIM";
["mediawiki/skins/Nostalgia"] = "SNOS";
["mediawiki/skins/Schulenburg"] = "SSCH";
["mediawiki/skins/Splash"] = "SSPL";
["mediawiki/skins/Synagonism"] = "SSYN";
["mediawiki/skins/Tomas"] = "STOM";
["mediawiki/skins/Truglass"] = "STRU";
["mediawiki/skins/Vector"] = "SVEC";
["mediawiki/skins/Apex"] = "SAPX";
["mediawiki/skins/Chameleon"] = "SCHA";
["mediawiki/skins/Erudite"] = "SERU";
["mediawiki/skins/Strapping"] = "SSTR";
["mediawiki/skins/p2wiki"] = "SPTW";
["mediawiki/skins/WebPlatform"] = "SWPL";
["operations/puppet"] = "OPUP";
["analytics/asana-stats"] = "ANAS";
["analytics/blog"] = "ANAB";
["analytics/camus"] = "ANAC";
["analytics/dashiki"] = "ANAD";
["analytics/data-warehouse"] = "ANDW";
["analytics/dclass"] = "ANDC";
["analytics/geowiki"] = "ANGW";
["analytics/geowiki-data-public"] = "ANGD";
["analytics/glass"] = "ANGL";
["analytics/global-dev-dashboard"] = "ANDE";
["analytics/global-dev-dashboard-data"] = "ANGF";
["analytics/kafkatee"] = "ANKA";
["analytics/kraken"] = "ANKR";
["analytics/kraken-deploy"] = "ANKD";
["analytics/libanon"] = "ANLA";
["analytics/libcidr"] = "ANLC";
["analytics/limn"] = "ANLI";
["analytics/limn-ee-data"] = "ANLE";
["analytics/limn-mobile-data"] = "ANLM";
["analytics/log2udp2"] = "ANLU";
["analytics/metrics"] = "ANME";
["analytics/multimedia"] = "ANMU";
["analytics/multimedia-config"] = "ANMC";
["analytics/pageview-api"] = "ANPA";
["analytics/quarry-web"] = "ANQW";
["analytics/refinery"] = "ANRE";
["analytics/refinery-source"] = "ANRS";
["analytics/reportcard"] = "ANRC";
["analytics/reportcard-data"] = "ANRD";
["analytics/snuggle"] = "ANSN";
["analytics/statsd-ganglia"] = "ANSG";
["analytics/tools-kripke"] = "ANTK";
["analytics/udp-filters"] = "ANUF";
["analytics/udplog"] = "ANUL";
["analytics/user-metrics"] = "ANUM";
["analytics/vagrant-build"] = "ANVB";
["analytics/vagrant-kraken"] = "ANVK";
["analytics/webstatscollector"] = "ANWC";
["analytics/wikihadoop"] = "ANWH";
["analytics/wikimetrics"] = "ANWM";
["analytics/wikistats"] = "ANWS";
["analytics/wp-zero"] = "ANZZ";
["analytics/zero-sms"] = "ANZS";
["apps/android-commons"] = "APAC";
["apps/android-java-mwapi"] = "APAJ";
["apps/android-translate"] = "APAT";
["apps/android-wikipedia"] = "APAW";
["apps/firefox-wikipedia"] = "APFW";
["apps/glass-wikipedia"] = "APGW";
["apps/ios-commons"] = "APIC";
["apps/ios-wikipedia"] = "APIW";
["apps/mobile-WikiLovesMonuments"] = "APWL";
["apps/win8-wikipedia"] = "APWW";
["glam-gwtoolset"] = "GLAM";
["integration/bundler"] = "CIBU";
["integration/composer"] = "CICP";
["integration/config"] = "CICF";
["integration/consistency"] = "CICS";
["integration/doc"] = "CIDC";
["integration/docroot"] = "CIDR";
["integration/jenkins"] = "CIJE";
["integration/jenkins-job-builder"] = "CIJJ";
["integration/jenkins-job-builder-config"] = "CIJC";
["integration/junitdiff"] = "CIJU";
["integration/phantomjs"] = "CIPJ";
["integration/php/coveralls"] = "CIPC";
["integration/phpcs"] = "CIPD";
["integration/phpunit"] = "CIPU";
["integration/zuul"] = "CIZU";
["integration/zuul-config"] = "CIZC";
["labs/centralauth"] = "LCAU";
["labs/incubator"] = "LINC";
["labs/invisible-unicorn"] = "LINU";
["labs/maps"] = "LMAP";
["labs/migration-assistant"] = "LMAS";
["labs/nagios-builder"] = "LNAB";
["labs/private"] = "LPRI";
["labs/qmwbot"] = "LQMW";
["labs/tools/labs"] = "LTOL";
["labs/tools/WMT"] = "TWMT";
["labs/tools/bub"] = "TBUB";
["labs/tools/connectivity"] = "TCON";
["labs/tools/coursestats"] = "TCST";
["labs/tools/extdist"] = "TEXD";
["labs/tools/gblrenamemon"] = "TGRM";
["labs/tools/giftbot"] = "TGFT";
["labs/tools/grrrit"] = "TGRT";
["labs/tools/guc"] = "TGUC";
["labs/tools/heritage"] = "THER";
["labs/tools/kirstentest"] = "TKIT";
["labs/tools/lists"] = "TLST";
["labs/tools/maintgraph"] = "TMTG";
["labs/tools/multichill"] = "TMUC";
["labs/tools/pywikibugs"] = "TPYW";
["labs/tools/signpost"] = "TSGN";
["labs/tools/wikicaptcha"] = "TWCA";
["labs/tools/wikipedia-android-builds"] = "TWAB";
["labs/tools/wikiviewstats"] = "TWVS";
["phabricator-Tools"] = "PHTO";
["operations/dns"] = "ODNS";
["VisualEditor/VisualEditor"] = "GVED";
["MicrosoftWebPlatformInstaller"] = "MWPI";
["FastStringSearch"] = "MFSS";
["NativePreprocessor"] = "MNPP";
["php/luasandbox"] = "MLUS";
["php/normal"] = "MNOR";
["php/wikidiff"] = "MWDI";
["php/wikidiff2"] = "MWDJ";
["php/wmerrors"] = "MWME";
["RCSub"] = "MRCS";
["mediawiki-ruby-api"] = "MRUB";
["mediawiki-selenium"] = "MSEL";
["bundles"] = "MBUN";
["code-utils"] = "MCUT";
["codesniffer"] = "MCSN";
["commonshelper2"] = "MCHT";
["fluoride"] = "MFLU";
["grabbers"] = "MGRA";
["missing-from-wikipedia"] = "MMFW";
["MediaWiki Release Tools"] = "MREL";
["RelEng"] = "MREN";
["scap"] = "MSCA";
["upload"] = "MUPL";
["mediawiki/vagrant"] = "MWVA";
["mediawiki/vendor"] = "MWVD";
["oojs"] = "GOJS";
["oojs/core"] = "GOJS";
["oojs/ui"] = "GOJU";
["openstack-wikistatus"] = "GOSW";
["openzim"] = "GOZI";
["operations/apache-config"] = "OAPA";
["operations/debs"] = "ODAA";
["operations/debs/StatsD"] = "ODAB";
["operations/debs/adminbot"] = "ODAC";
["operations/debs/archiva"] = "ODAD";
["operations/debs/check_ganglia"] = "ODAE";
["operations/debs/contenttranslation"] = "ODAF";
["operations/debs/contenttranslation-apertium"] = "ODAG";
["operations/debs/contenttranslation-apertium-apy"] = "ODAH";
["operations/debs/contenttranslation-apertium-br-fr"] = "ODAI";
["operations/debs/contenttranslation-apertium-en-ca"] = "ODAJ";
["operations/debs/contenttranslation-apertium-en-es"] = "ODAK";
["operations/debs/contenttranslation-apertium-es-ca"] = "ODAL";
["operations/debs/contenttranslation-apertium-es-pt"] = "ODAM";
["operations/debs/contenttranslation-apertium-fr-ca"] = "ODAN";
["operations/debs/contenttranslation-apertium-fr-es"] = "ODAO";
["operations/debs/contenttranslation-apertium-lex-tools"] = "ODAP";
["operations/debs/contenttranslation-apertium-pt-ca"] = "ODAQ";
["operations/debs/contenttranslation-apertium-sv-da"] = "ODAR";
["operations/debs/contenttranslation-cg3"] = "ODAS";
["operations/debs/contenttranslation-lttoolbox"] = "ODAT";
["operations/debs/etherpad-lite"] = "ODAU";
["operations/debs/flask-login"] = "ODAV";
["operations/debs/ganglia"] = "ODAW";
["operations/debs/git-deploy"] = "ODAX";
["operations/debs/git-fat"] = "ODAY";
["operations/debs/hhvm"] = "ODAZ";
["operations/debs/ircd-ratbox"] = "ODBA";
["operations/debs/ircecho"] = "ODBB";
["operations/debs/jenkins-debian-glue"] = "ODBC";
["operations/debs/jmxtrans"] = "ODBD";
["operations/debs/kafka"] = "ODBE";
["operations/debs/kafkacat"] = "ODBF";
["operations/debs/latexml"] = "ODBG";
["operations/debs/libanon"] = "ODBH";
["operations/debs/libav"] = "ODBI";
["operations/debs/librsvg"] = "ODBJ";
["operations/debs/libvpx"] = "ODBK";
["operations/debs/logstash-gelf"] = "ODBL";
["operations/debs/logster"] = "ODBM";
["operations/debs/lucene-search-2"] = "ODBN";
["operations/debs/mariadb-server"] = "ODBO";
["operations/debs/memkeys"] = "ODBP";
["operations/debs/mod_tile"] = "ODBR";
["operations/debs/mwbzutils"] = "ODBS";
["operations/debs/mysqlatfacebook"] = "ODBT";
["operations/debs/nginx"] = "ODBU";
["operations/debs/nodejs"] = "ODBV";
["operations/debs/osm-mapnik-style"] = "ODBW";
["operations/debs/osm2pgsql"] = "ODBX";
["operations/debs/phantomjs"] = "ODBY";
["operations/debs/php/mailparse"] = "ODBZ";
["operations/debs/puppet"] = "ODCA";
["operations/debs/pybal"] = "ODCB";
["operations/debs/python-diamond"] = "ODCC";
["operations/debs/python-flask-login"] = "ODCD";
["operations/debs/python-gear"] = "ODCE";
["operations/debs/python-jsonschema"] = "ODCF";
["operations/debs/python-kafka"] = "ODCG";
["operations/debs/python-phabricator"] = "ODCH";
["operations/debs/python-statsd"] = "ODCI";
["operations/debs/quickstack"] = "ODCJ";
["operations/debs/rt-authen-externalauth"] = "ODCK";
["operations/debs/ruby-dimensions"] = "ODCL";
["operations/debs/ruby-execjs"] = "ODCM";
["operations/debs/ruby-jsduck"] = "ODCN";
["operations/debs/ruby-parallel"] = "ODCO";
["operations/debs/sartoris"] = "ODCP";
["operations/debs/search-qa"] = "ODCQ";
["operations/debs/squid"] = "ODCR";
["operations/debs/stud"] = "ODCS";
["operations/debs/udp2log-log4j-java"] = "ODCT";
["operations/debs/utfnormal"] = "ODCU";
["operations/debs/varnish"] = "ODCV";
["operations/debs/vips"] = "ODCW";
["operations/debs/wikibugs"] = "ODCX";
["operations/debs/wikimedia/base"] = "ODCY";
["operations/debs/wikimedia/job-runner"] = "ODCZ";
["operations/debs/wikimedia/keyring"] = "ODDA";
["operations/debs/wikimedia/ldap-tools"] = "ODDB";
["operations/debs/wikimedia/lvs-realserver"] = "ODDC";
["operations/debs/wikimedia/search-qa"] = "ODDD";
["operations/debs/wikimedia/task-appserver"] = "ODDE";
["operations/debs/wikistats"] = "ODDF";
["operations/dumps"] = "ODUM";
["operations/dumps-archiving"] = "ODUA";
["operations/dumps-incremental"] = "ODUI";
["operations/dumps-test"] = "ODUT";
["operations/mediawiki-config"] = "OMWC";
["operations/mediawiki-multiversion"] = "OMWM";
["operations/network-diagrams"] = "ONET";
["operations/puppet/cassandra"] = "OPCA";
["operations/puppet/cdh"] = "OPCD";
["operations/puppet/cdh4"] = "OPCF";
["operations/puppet/jmxtrans"] = "OPJM";
["operations/puppet/kafka"] = "OPKA";
["operations/puppet/kafkatee"] = "OPKT";
["operations/puppet/mariadb"] = "OPMD";
["operations/puppet/nginx"] = "OPNG";
["operations/puppet/varnish"] = "OPVA";
["operations/puppet/varnishkafka"] = "OPVK";
["operations/puppet/wikimetrics"] = "OPWM";
["operations/puppet/zookeeper"] = "OPZK";
["operations/software/elasticsearch-plugins"] = "OSEP";
["operations/software/ganglia-logtailer"] = "OSGL";
["operations/software/ganglios"] = "OSGA";
["operations/software/gdash"] = "OSGD";
["operations/software/grafana"] = "OSGR";
["operations/software/hhvm-dev"] = "OSHD";
["operations/software/hhvm-dev-folly"] = "OSHF";
["operations/software/hhvm-dev-third-party"] = "OSHT";
["operations/software/kibana"] = "OSKI";
["operations/software/librenms"] = "OSLR";
["operations/software/mwprof"] = "OSMP";
["operations/software/mwprof-reporter"] = "OSMR";
["operations/software/otrs"] = "OSOT";
["operations/software/redactatron"] = "OSRE";
["operations/software/shinkengen"] = "OSHI";
["operations/software/swift-ring"] = "OSWI";
["operations/software/varnish-libvmod-netmapper"] = "OSVL";
["operations/software/varnish-varnishkafka"] = "OSVV";
["operations/software/varnish-vhtcpd"] = "OSVH";
["passport-mediawiki"] = "GPMW";
["qa/browsertests"] = "GQAB";
["qrpedia"] = "GQRP";
["sandbox"] = "GSAN";
["sartoris"] = "GSAR";
["search-extra"] = "GSXT";
["search-highlighter"] = "GSHI";
["search-repository-swift"] = "GSRS";
["translatewiki"] = "GTWN";
["unicodejs"] = "GUJS";
["user-metrics-2"] = "GUMT";
["wikimedia/TransparencyReport"] = "WTRR";
["wikimedia/WikimediaShopTools"] = "WMST";
["wikimedia/bots-LabsAntiSpamBot"] = "GLAS";
["wikimedia/bots-WMIB"] = "GWMI";
["wikimedia/bots-jouncebot"] = "GJOU";
["wikimedia/communications-WMBlog"] = "WMBL";
["wikimedia/communications-WP-Victor"] = "WPVI";
["wikimedia/fundraising/FineDiff"] = "WFID";
["wikimedia/fundraising/LanguageTag"] = "WFLT";
["wikimedia/fundraising/LoveMap"] = "WFLM";
["wikimedia/fundraising/PaymentsListeners"] = "WFPL";
["wikimedia/fundraising/SmashPig"] = "WFSP";
["wikimedia/fundraising/SmashPig-vendor"] = "WFSV";
["wikimedia/fundraising/civicrm"] = "WFCA";
["wikimedia/fundraising/civicrm/buildkit"] = "WFCB";
["wikimedia/fundraising/civicrm/buildkit-vendor"] = "WFCC";
["wikimedia/fundraising/civicrm/buildkit-vendor-totten"] = "WFCD";
["wikimedia/fundraising/civicrm/buildkit-vendor-totten-amp"] = "WFCE";
["wikimedia/fundraising/civicrm/buildkit-vendor-totten-git-scan"] = "WFCF";
["wikimedia/fundraising/crm"] = "WFCG";
["wikimedia/fundraising/crm-civicrm"] = "WFCH";
["wikimedia/fundraising/crm-drupal"] = "WFCI";
["wikimedia/fundraising/crm-drush"] = "WFCJ";
["wikimedia/fundraising/crm-modules"] = "WFCK";
["wikimedia/fundraising/crm-modules-dedupe_review"] = "WFCL";
["wikimedia/fundraising/crm-vendor"] = "WFCM";
["wikimedia/fundraising/dash"] = "WFDA";
["wikimedia/fundraising/dash-node_modules"] = "WFDM";
["wikimedia/fundraising/dash-src"] = "WFDS";
["wikimedia/fundraising/dash-src-bower_modules"] = "WFDB";
["wikimedia/fundraising/phpmailer"] = "WFPM";
["wikimedia/fundraising/slander"] = "WFSL";
["wikimedia/fundraising/stomp"] = "WFST";
["wikimedia/fundraising/tools"] = "WFTO";
["wikimedia/fundraising/tools-DjangoBannerStats"] = "WFTD";
["wikimedia/fundraising/twig"] = "WFTW";
["wikimedia/iegreview"] = "WIEG";
["wikimedia/lobbypop"] = "WLOB";
["wikimedia/orgchart"] = "WORG";
["wikimedia/roadmap-updater"] = "WRUP";
["wikimedia/wikimania-scholarships"] = "WWSC";
["wikimedia/wlm-api"] = "GWLA";
["wiktionary-anagrimes"] = "GWAN";
["winter"] = "GWIN";
["winter-snowflakes"] = "GWIS";
["xowa"] = "GXOW";
["Subversion"] = "SVN";
["pywikibot/bot-CommonsDelinker"] = "PWCD";
["pywikibot/bot-catbot"] = "PWCB";
["pywikibot/bot-drtrigonbot"] = "PWDT";
["pywikibot/bot-misc"] = "PWMI";
["pywikibot/bot-ragesossbot"] = "PWRA";
["pywikibot/compat"] = "PWBO";
["pywikibot"] = "PWBC";
["pywikibot/core"] = "PWBC";
["pywikibot/external-httplib2"] = "PWXH";
["pywikibot/i18n"] = "PWIN";
["pywikibot/opencv"] = "PWXO";
["pywikibot/pycolorname"] = "PWXC";
["pywikibot/sf-export"] = "PWSE";
["pywikibot/spelling"] = "PWSP";
["pywikibot/wiktionary"] = "PWKT";
["phabricator-Sprint"] = "PHSP";
["cdb"] = "CDB";
["extensions"] = "MEXT";
["operations/software/dbtree"] = "OSDB";
["operations/software/dropwizard-metrics"] = "OSDM";
["operations/software/ircyall"] = "OSIY";
["operations/software/labsdb-auditor"] = "OSLA";
["operations/software/puppet-compiler"] = "OSPC";
["operations/software/rescue-pxe"] = "OSPX";
["operations/software/statsdlb"] = "OSSD";
["operations/software/swift-utils"] = "OSSU";
["pywikiapi"] = "PWAP";
["pywikibot/externals"] = "PWEX";
["utfnormal"] = "GUTF";
["wikidata-gremlin"] = "GWDG";
["wikimedia/annualreport"] = "WANR";
["wikimedia/education-WikiEduDashboard"] = "WEDD";
["pywikibot/bots-mjbmrbot"] = "PWBM";
["mediawiki/skins/Empty"] = "SEMP";
["mediawiki/skins/Slate"] = "SLAT";
["mediawiki/skins/Tempo"] = "STEM";
["mediawiki/skins"] = "SKIN";
["cxserver"] = "GCIT";
["cxserver-deploy"] = "GCID";
["cxserver"] = "GCXS";
["cxserver-deploy"] = "GCXD";
["jobrunner"] = "GJOB";
["mathoid"] = "GMAT";
["ocg-collection"] = "GOCG";
["mediawiki/services/parsoid"] = "GPAR";
["parsoid-deploy"] = "GPAD";
["restbase-deploy"] = "GRBD";
["rcstream"] = "GSTR";
["phabricator-BurnDownCharts"] = "PHBD";
["mediawiki/services/hierator"] = "GHIE";
["mediawiki/services/rashomon"] = "GRAS";
["mediawiki/services/restbase"] = "GRES";
["mediawiki/services/service-runner"] = "GSER";
["mediawiki/services/service-template-node"] = "GSTN";
["mediawiki/services/tardist"] = "GTAR";
["mediawiki/services/zotero-translation-server"] = "GZTS";
["mediawiki/services/zotero-translators"] = "GZTT";
["mediawiki/services/graphoid"] = "GGRA";
["mediawiki/services/graphoid-deploy"] = "GGRD";
["php/tidy"] = "MTID";
["phabricator-Security"] = "PHES";
["analytics/aggregator"] = "ANAG";
["analytics/gerrit-stats"] = "ANGS";
["analytics/gerrit-stats-data"] = "AGSD";
["analytics/limn-flow-data"] = "ANLF";
["analytics/limn-language-data"] = "ANLL";
["analytics/mediawiki-storage"] = "ANMS";
["analytics/proof-of-concept"] = "ANPC";
["analytics/statsv"] = "ANSV";
["analytics/ua-parser"] = "ANUA";
["analytics/limn-edit-data"] = "ANLD";
["analytics/abacist"] = "ANBC";
["analytics/aggregator-data"] = "ANAR";
["mediawiki/extensions/ApiFeatureUsage"] = "EAFU";
["mediawiki/extensions/ArticleComments"] = "EACO";
["mediawiki/extensions/BoilerPlate"] = "EBOP";
["mediawiki/extensions/Buggy"] = "EBUG";
["mediawiki/extensions/CollapsibleVector"] = "ECLV";
["mediawiki/extensions/DonationInterface-vendor"] = "EDIV";
["mediawiki/extensions/EditAccount"] = "EEDA";
["mediawiki/extensions/Farmer"] = "EFRM";
["mediawiki/extensions/Favorites"] = "EFAV";
["mediawiki/extensions/Gather"] = "EGAT";
["mediawiki/extensions/GitHub"] = "EGIT";
["mediawiki/extensions/GoogleAPIClient"] = "EGAC";
["mediawiki/extensions/GoogleAnalyticsTopPages"] = "EATP";
["mediawiki/extensions/HitCounters"] = "EHTC";
["mediawiki/extensions/Html2Wiki"] = "EHTW";
["mediawiki/extensions/LDAPAuthorization"] = "ELDP";
["mediawiki/extensions/LinkSuggest2"] = "ELNS";
["mediawiki/extensions/Link_Attributes"] = "ELNA";
["mediawiki/extensions/MsCatSelect"] = "EMSC";
["mediawiki/extensions/MsInsert"] = "EMSI";
["mediawiki/extensions/MsWikiEditor"] = "EMSE";
["mediawiki/extensions/MultiBoilerplate"] = "EMBP";
["mediawiki/extensions/OOUIPlayground"] = "EUIP";
["mediawiki/extensions/OpenIDConnect"] = "EIDC";
["mediawiki/extensions/PagesList"] = "EPGL";
["mediawiki/extensions/PluggableAuth"] = "EPLG";
["mediawiki/extensions/RestBaseUpdateJobs"] = "ERBU";
["mediawiki/extensions/RevealEmail"] = "ERVE";
["mediawiki/extensions/SemanticBreadcrumbLinks"] = "ESBL";
["mediawiki/extensions/SemanticDependency"] = "ESDP";
["mediawiki/extensions/SemanticInterlanguageLinks"] = "ESIL";
["mediawiki/extensions/SimpleSAMLphp"] = "ESAM";
["mediawiki/extensions/ViewportMetrics"] = "EVPM";
["mediawiki/extensions/VikiSemanticTitle"] = "EVST";
["mediawiki/extensions/VikiTitleIcon"] = "EVTI";
["mediawiki/extensions/VirtualKeyboard"] = "EVTK";
["mediawiki/extensions/WhosOnline"] = "EWHO";
["mediawiki/extensions/WikibaseJavaScriptApi"] = "EWBJ";
["mediawiki/extensions/WikibaseRepository"] = "EWBR";
["mediawiki/extensions/WikibaseView"] = "EWBV";
["mediawiki/extensions/WikidataQuality"] = "EWQL";
["mediawiki/extensions/Cargo"] = "ECRG";
["mediawiki/extensions/ContributionsList"] = "ECNL";
["mediawiki/extensions/ContributorsAddon"] = "ECNA";
["mediawiki/extensions/PaginateText"] = "EPTX";
["mediawiki/extensions/PlanOut"] = "EPLO";
["mediawiki/extensions/SemanticMetaTags"] = "ESME";
["mediawiki/extensions/Sentry"] = "ESNT";
["labs/tools/SuchABot"] = "TSUB";
["labs/tools/faces"] = "TFCS";
["labs/tools/gerrit-to-redis"] = "TGTR";
["labs/tools/phabricator-bug-status"] = "TPBS";
["labs/tools/wikibugs2"] = "TWBT";
["phabricator-extensions"] = "PHEX";
["test-gerrit-ping"] = "GGTP";
["wmf-utils"] = "GUTI";
["mediawiki/tools/Cite4Wiki"] = "MCFW";
["mediawiki/tools/dippybird"] = "MDIP";
["mediawiki/tools/mwdumper"] = "MWDU";
["mediawiki/tools/schroot"] = "MSRT";
["mediawiki/tools/upload/PhotoUpload"] = "MUPU";
["phabricator-test"] = "PHTE";
["openstack-designate"] = "GOSD";
["sink_nova_fixed_multi"] = "GSNF";
["sink_nova_ldap"] = "GSNL";
["operations/debs/avconv10"] = "ODDG";
["operations/debs/carbon-c-relay"] = "ODDH";
["operations/debs/contenttranslation-apertium-eo-en"] = "ODDI";
["operations/debs/contenttranslation-apertium-hbs"] = "ODDJ";
["operations/debs/contenttranslation-apertium-hbs-eng"] = "ODDK";
["operations/debs/contenttranslation-apertium-hbs-mkd"] = "ODDL";
["operations/debs/contenttranslation-apertium-hbs-slv"] = "ODDM";
["operations/debs/contenttranslation-apertium-hin"] = "ODDN";
["operations/debs/contenttranslation-apertium-id-ms"] = "ODDO";
["operations/debs/contenttranslation-apertium-mk"] = "ODDP";
["operations/debs/contenttranslation-apertium-mk-bg"] = "ODDQ";
["operations/debs/contenttranslation-apertium-nno"] = "ODDR";
["operations/debs/contenttranslation-apertium-nno-nob"] = "ODDS";
["operations/debs/contenttranslation-apertium-nob"] = "ODDT";
["operations/debs/contenttranslation-apertium-urd"] = "ODDU";
["operations/debs/contenttranslation-apertium-urd-hin"] = "ODDV";
["operations/debs/ffmpeg2theorawmf"] = "ODDW";
["operations/debs/gerrit"] = "ODDX";
["operations/debs/nutcracker"] = "ODDY";
["operations/debs/opus"] = "ODDZ";
["operations/debs/perf-tools"] = "ODEA";
["operations/debs/statsite"] = "ODEB";
["operations/debs/txstatsd"] = "ODEC";
["operations/debs/contenttranslation/apertium-af-nl"] = "ODED";
["operations/debs/contenttranslation/apertium-dan"] = "ODEE";
["operations/debs/contenttranslation/apertium-dan-nor"] = "ODEF";
["operations/debs/contenttranslation/apertium-en-gl"] = "ODEG";
["operations/debs/contenttranslation/apertium-es-an"] = "ODEH";
["operations/debs/contenttranslation/apertium-es-ast"] = "ODEI";
["operations/debs/contenttranslation/apertium-es-gl"] = "ODEJ";
["operations/debs/contenttranslation/apertium-eu-en"] = "ODEK";
["operations/debs/contenttranslation/apertium-eu-es"] = "ODEL";
["operations/debs/contenttranslation/apertium-eus"] = "ODEM";
["operations/debs/contenttranslation/apertium-kaz"] = "ODEN";
["operations/debs/contenttranslation/apertium-kaz-tat"] = "ODEO";
["operations/debs/contenttranslation/apertium-oc-ca"] = "ODEP";
["operations/debs/contenttranslation/apertium-oc-es"] = "ODEQ";
["operations/debs/contenttranslation/apertium-pt-gl"] = "ODER";
["operations/debs/contenttranslation/apertium-tat"] = "ODES";
["operations/debs/contenttranslation/hfst"] = "ODET";
["operations/debs/jetty-runner"] = "ODEU";
["operations/debs/nodepool"] = "ODEV";
["mediawiki/extensions/LastUserLogin"] = "ELUL";
["mediawiki/extensions/MadLib"] = "EMLI";
["mediawiki/extensions/MassAction"] = "EMSA";
["mediawiki/extensions/RawImageHandler"] = "ERIH";
["mediawiki/extensions/SafeDelete"] = "ESDL";
["mediawiki/extensions/WikidataPageBanner"] = "EWDP";
["mediawiki/extensions/MsCalendar"] = "EMCL";
["mediawiki/skins/Blueprint"] = "SBLU";
["gerrit"] = "GGER";
["labs/tools/Wikidipendenza"] = "TWDI";
["labs/tools/Faces"] = "TFACES";
["labs/tools/ptable"] = "TPTAB";
}

local p = {}

function p.repoToCallsign( frame )
    local repo = frame.args[1]
    return callsigns[repo]
end

return p</text>
    <sha1>494ef077ac3753140476cb0d9a273c4c33fd2c1d</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Module:Callsigns/doc</title>
  <ns>0</ns>
  <id>95</id>
  <revision>
    <id>233</id>
    <timestamp>2016-01-06T06:40:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This module maps each ''repository path'' in [[Gerrit]] to its "callsign" in [[Diffusion]]. {{tl|git file}} ([[phab:T101358]]) and other templates use it.  When you create, re..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="852" xml:space="preserve">This module maps each ''repository path'' in [[Gerrit]] to its "callsign" in [[Diffusion]].
{{tl|git file}} ([[phab:T101358]]) and other templates use it.

When you create, rename, or reorganize a new repository, you need to update this mapping.

Note a repository path is different from the repository name in Diffusion.
You see this path in some gerrit URLs, in the "Project ''path/here''" heading on some gerrit pages, and in the "Clone" command in the Diffusion summary.
For example, "oojs-ui" in Diffusion has the callsign GOJU, and on the [[phab:diffusion/GOJU]] page its Clone command is &lt;kbd&gt;&lt;nowiki&gt;https://&lt;/nowiki&gt;gerrit.wikimedia.org/r/p/'''oojs/ui'''&lt;/kbd&gt;. So its path is &lt;code&gt;oojs/ui&lt;/code&gt;, and this matches the path in gerrit URLs like https://gerrit.wikimedia.org/r/#/projects/oojs/ui,dashboards/default and their "Project" headings.</text>
    <sha1>a1a9d77639d4256ac3f51bfd588a8e050e73f1e5</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Gerrit</title>
  <ns>0</ns>
  <id>96</id>
  <revision>
    <id>234</id>
    <timestamp>2016-01-06T06:42:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;languages /&gt; __NOTOC__ [[File:Gerrit.svg|{{dir|{{pagelang}}|left|right}}|200px]] File:Gerrit.wikimedia.org as seen on 2013-03-05 14 08 23.png|thumb|&lt;translate&gt;&lt;!--T:1--&gt; A..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3935" xml:space="preserve">&lt;languages /&gt;
__NOTOC__
[[File:Gerrit.svg|{{dir|{{pagelang}}|left|right}}|200px]]
[[File:Gerrit.wikimedia.org as seen on 2013-03-05 14 08 23.png|thumb|&lt;translate&gt;&lt;!--T:1--&gt;
A view of open change sets at [&lt;tvar|gerrit&gt;https://gerrit.wikimedia.org&lt;/&gt; gerrit.wikimedia.org]&lt;/translate&gt;]]
{{TNT|Git and Gerrit}}
&lt;translate&gt;
&lt;!--T:2--&gt;
Code review is at the heart of our development process. Any software contribution to [[&lt;tvar|whatis&gt;Special:MyLanguage/Manual:What is MediaWiki?&lt;/&gt;|MediaWiki]] or any other Wikimedia hosted project is reviewed and approved at [https://gerrit.wikimedia.org gerrit.wikimedia.org] before being merged to our [[w:Git (software)|Git]] repositories. The tool we use to handle code reviews is [[w:Gerrit_(software)|Gerrit]].

&lt;!--T:3--&gt;
All [[&lt;tvar|dev-access&gt;Special:MyLanguage/Developer access&lt;/&gt;|Gerrit users]] can review contributions but only [[&lt;tvar|maintainers&gt;Developers/Maintainers&lt;/&gt;|maintainers]] have the [[&lt;tvar|plus2&gt;Gerrit/+2&lt;/&gt;|special rights]] to approve or reject them.

== Getting started == &lt;!--T:4--&gt;

&lt;!--T:16--&gt;
To quickly get a functioning pre-configured development installation of MediaWiki, including a virtual machine, MediaWiki source code, as well as all prerequisites and (optionally) various extensions, see [[MediaWiki-Vagrant]]. This is the recommended way of getting started with MediaWiki development.

&lt;!--T:5--&gt;
To simply '''browse &amp; fork our code''' you can use the [&lt;tvar|github&gt;https://github.com/wikimedia&lt;/&gt; GitHub mirror].

&lt;!--T:6--&gt;
To make an anonymous git clone of core MediaWiki, &lt;tvar|gerrit&gt;&lt;kbd&gt;git clone https://gerrit.wikimedia.org/r/p/mediawiki/core.git&lt;/kbd&gt;&lt;/&gt;

&lt;!--T:7--&gt;
To '''submit your first patch''' check the [[&lt;tvar|tutorial&gt;Gerrit/Tutorial&lt;/&gt;|tutorial]] or its [[&lt;tvar|getting-started&gt;Gerrit/Getting started&lt;/&gt;|shorter version]].

&lt;!--T:8--&gt;
Your '''help reviewing changes''' is welcome! [[&lt;tvar|tutorial&gt;Gerrit/Tutorial#How we review code&lt;/&gt;|Learn how]].

== Tutorials &amp; guidelines == &lt;!--T:9--&gt;

&lt;!--T:10--&gt;
Other useful documentation written for MediaWiki &amp; Wikimedia developers:

&lt;!--T:11--&gt;
* Setting up [[MediaWiki-Vagrant|Vagrant]] virtual machine development environment.
* [[Gerrit/Commit message guidelines|Commit message guidelines]]
* [[Gerrit/Code review|Code review guide]]
* [[Gerrit/Navigation|Gerrit interface navigation]]
* [&lt;tvar|gerrit-index&gt;https://gerrit.wikimedia.org/r/Documentation/index.html&lt;/&gt; Gerrit's documentation]
* [&lt;tvar|gerrit-search&gt;https://gerrit.wikimedia.org/r/Documentation/user-search.html&lt;/&gt; Searching in Gerrit]
* [[Gerrit/Advanced usage|Advanced usage]]

== Special cases == &lt;!--T:12--&gt;

&lt;!--T:13--&gt;
* [[Gerrit/New repositories|Requesting new repositories]]
* [[Gerrit/Project ownership|Project owners]]
* [[Gerrit/+2|Reviewers with merging rights]]

== See also == &lt;!--T:14--&gt;

&lt;!--T:15--&gt;
* [https://gerrit.wikimedia.org/r/#/admin/projects/ List of the public Gerrit projects]
* [[wikitech:Gerrit|Technical information about Wikimedia's Gerrit installation]]
* [https://phabricator.wikimedia.org/maniphest/task/create/?projects=Gerrit Report bugs/other issues with Gerrit]
** [https://phabricator.wikimedia.org/maniphest/task/create/?projects=Gitblit Report bugs/other issues with the Gitblit web interface at git.wikimedia.org]
* [[phab:37497]] - Implement a way to bring GitHub pull requests into Gerrit.
** [[User:Yuvipanda/G2G|G2G]], a set of scripts that make Gerrit / GitHub interoperability possible.
** [https://gist.github.com/yuvipanda/5174162 sync-gerrit.bash] script to move GitHub pull requests to Gerrit Changeset manually ([http://lists.wikimedia.org/pipermail/wikitech-l/2013-March/067665.html discussion]).
* [https://tools.wmflabs.org/gerrit-patch-uploader/ Wikimedia Gerrit Patch Uploader]
* [[wikitech:grrrit-wm|grrrit-wm]]
* [[wikitech:Gerrit Notification Bot|Gerrit Notification Bot]]
&lt;/translate&gt;

[[Category:Gerrit{{translation}}]]
[[Category:New contributors{{translation}}]]</text>
    <sha1>4d14acccedca6f2afbc453bc28502f0c7ad6e305</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>File:Gerrit.wikimedia.org as seen on 2013-03-05 14 08 23.png</title>
  <ns>6</ns>
  <id>97</id>
  <revision>
    <id>235</id>
    <timestamp>2016-01-06T06:43:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>236</id>
    <parentid>235</parentid>
    <timestamp>2016-01-06T06:44:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie uploaded a new version of [[File:Gerrit.wikimedia.org as seen on 2013-03-05 14 08 23.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>237</id>
    <parentid>236</parentid>
    <timestamp>2016-01-06T06:46:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie uploaded a new version of [[File:Gerrit.wikimedia.org as seen on 2013-03-05 14 08 23.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>File:Gerrit.svg</title>
  <ns>6</ns>
  <id>98</id>
  <revision>
    <id>238</id>
    <timestamp>2016-01-06T06:48:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>239</id>
    <parentid>238</parentid>
    <timestamp>2016-01-06T06:49:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie uploaded a new version of [[File:Gerrit.svg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160101031211|194">
  <title>Category:Mediawiki.org Formatting templates</title>
  <ns>14</ns>
  <id>100</id>
  <revision>
    <id>242</id>
    <parentid>241</parentid>
    <timestamp>2016-01-06T06:55:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="33" xml:space="preserve">[[Category:Formatting templates]]</text>
    <sha1>b0977d99bfd84d652e4508b3691eb776cf54a6dd</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Grey</title>
  <ns>10</ns>
  <id>101</id>
  <revision>
    <id>244</id>
    <parentid>243</parentid>
    <timestamp>2016-01-06T06:55:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="390" xml:space="preserve">&lt;span style="color:#999;"&gt;{{{1}}}&lt;/span&gt;&lt;noinclude&gt;

* See also: {{tl|s}}

[[Category:Formatting templates|{{PAGENAME}}]]

&lt;templatedata&gt;
{
	"description": "Display text in gray",
	"params": {
		"1": {
			"label": "Text",
			"description": "Text to be displayed",
			"type": "string",
			"default": "text",
			"suggested": true,
			"autovalue": "value"
		}
	}
}
&lt;/templatedata&gt;
&lt;/noinclude&gt;</text>
    <sha1>629dd57a007f80942599a00e027948fcedfcb97c</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Category:Cross-browser compatibility templates</title>
  <ns>14</ns>
  <id>102</id>
  <revision>
    <id>246</id>
    <parentid>245</parentid>
    <timestamp>2016-01-06T06:55:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="114" xml:space="preserve">This category lists all templates that facilitate in cross-browser CSS support.

[[Category:Formatting templates]]</text>
    <sha1>e44d93c6a7bddb9c36f79fab0f7dadb21bbe1bf0</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Phpi</title>
  <ns>10</ns>
  <id>103</id>
  <revision>
    <id>248</id>
    <parentid>247</parentid>
    <timestamp>2016-01-06T06:55:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="277" xml:space="preserve">{{inline-code|{{{1}}}|lang=php}}&lt;noinclude&gt;
&lt;templatedata&gt;
{
	"params": {
		"1": {
			"label": "Content",
			"description": "The PHP program code to be displayed.",
			"type": "string",
			"required": true
		}
	}
}
&lt;/templatedata&gt;
[[Category:Formatting templates]]
&lt;/noinclude&gt;</text>
    <sha1>10be38885e779a372c5765a3b22ba9aaad06850e</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Jsi</title>
  <ns>10</ns>
  <id>104</id>
  <revision>
    <id>250</id>
    <parentid>249</parentid>
    <timestamp>2016-01-06T06:55:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="158" xml:space="preserve">{{inline-code|{{{1}}}|lang=javascript}}&lt;noinclude&gt;

Invokes {{tl|inline-code}} with &lt;code&gt;lang=javascript&lt;/code&gt;
[[Category:Formatting templates]]&lt;/noinclude&gt;</text>
    <sha1>5830e6fb23f49e101e38b7861f4daa0304a55e40</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Inline-code</title>
  <ns>10</ns>
  <id>105</id>
  <revision>
    <id>252</id>
    <parentid>251</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="340" xml:space="preserve">{{#tag:syntaxhighlight|{{{1|input}}}|lang={{{lang|php}}}|enclose=none}}&lt;noinclude&gt;

== Usage ==
: Some text, then &lt;nowiki&gt;{{Inline-code | 1=wfDebug( $text, $dest = 'all' );}}&lt;/nowiki&gt; and more text.

produces
:Some text, then {{Inline-code | 1=wfDebug( $text, $dest = 'all' );}} and more text.

[[Category:Formatting templates]]&lt;/noinclude&gt;</text>
    <sha1>b60139d46d6d072f26f3ea63670145f9b31a9fe6</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:S</title>
  <ns>10</ns>
  <id>106</id>
  <revision>
    <id>254</id>
    <parentid>253</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="179" xml:space="preserve">&lt;span style="text-decoration:line-through; color:#999"&gt;{{{1|striked text}}}&lt;/span&gt;&lt;noinclude&gt;

* See also: {{tl|grey}}

[[Category:Formatting templates|{{PAGENAME}}]]
&lt;/noinclude&gt;</text>
    <sha1>8e444119abfd7aa3c1cdc49424b59145293dabd4</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Green</title>
  <ns>10</ns>
  <id>107</id>
  <revision>
    <id>256</id>
    <parentid>255</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="111" xml:space="preserve">&lt;span style="color:green"&gt;{{{1}}}&lt;/span&gt;&lt;noinclude&gt;
[[Category:Formatting templates|{{PAGENAME}}]]
&lt;/noinclude&gt;</text>
    <sha1>5fce00bbe0789ccf092ee46ffbef5e1c16127e2f</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Red</title>
  <ns>10</ns>
  <id>108</id>
  <revision>
    <id>258</id>
    <parentid>257</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="113" xml:space="preserve">&lt;span style="color:#BA0000"&gt;{{{1}}}&lt;/span&gt;&lt;noinclude&gt;
[[Category:Formatting templates|{{PAGENAME}}]]
&lt;/noinclude&gt;</text>
    <sha1>679ceced3c067adf7b211de86ff810db7cd49c55</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Blue</title>
  <ns>10</ns>
  <id>109</id>
  <revision>
    <id>260</id>
    <parentid>259</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="167" xml:space="preserve">&lt;noinclude&gt;
{{languages}}
&lt;/noinclude&gt;&lt;span style="color:#0645AD;"&gt;{{{1}}}&lt;/span&gt;&lt;noinclude&gt;
[[Category:Formatting templates{{translation}}|{{PAGENAME}}]]
&lt;/noinclude&gt;</text>
    <sha1>3300263cd97853e64e01cf269e5c1e5cde832838</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Collapse top</title>
  <ns>10</ns>
  <id>110</id>
  <revision>
    <id>262</id>
    <parentid>261</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1457" xml:space="preserve">&lt;noinclude&gt;
{{languages}}
&lt;/noinclude&gt;&lt;div style="display:{{{display|block}}};margin-{{dir|{{pagelang}}|right|left}}:{{{indent|0px}}};{{{extrastyle|}}}"&gt;&lt;!-- NOTE: width renders incorrectly if added to main STYLE section--&gt;
{| &lt;!-- Template:Collapse top --&gt; class="navbox mw-collapsible {{{{{|safesubst:}}}#if:{{{expand|}}}||mw-collapsed}}" style="background: {{{bg1|transparent}}}; text-align: {{dir|{{pagelang}}|right|left}}; border: {{{border|1px}}} solid {{{b-color|silver}}}; margin-top: 0.2em; {{{{{|safesubst:}}}#if:{{{width|}}}|width:{{{width}}};}}"
|-
! style="background-color: {{{bg|#F8FCFF}}}; text-align:{{{{{|safesubst:}}}#if:{{{left|}}}|{{dir|{{pagelang}}|right|left}}|center}}; font-size:112%; color: {{{fc|black}}};" | {{{1|{{{title|{{{reason|{{{header|{{{heading|Extended content}}} }}} }}} }}} }}}   
{{{{{|safesubst:}}}#if:{{{warning|{{{2|}}}}}}
|{{{{{|safesubst:}}}!}}-
{{{{{|safesubst:}}}!}} style="text-align:center; font-style:italic;" {{{{{|safesubst:}}}!}} {{{2|The following is a closed debate. {{strongbad|Please do not modify it.}} }}} }}
|-
| style="border: solid {{{border2|1px silver}}}; padding: {{{padding|8px}}}; background-color: {{{bg2|white}}}; font-size:112%;" {{{{{|safesubst:}}}!}}&lt;noinclude&gt;
&lt;center&gt;''The following content has been placed in a collapsed box for improved usability.''&lt;/center&gt;
{{ {{TNTN|Collapse bottom}} }}
{{ {{TNTN|Documentation}} }}
[[Category:Formatting templates{{translation}}]]
&lt;/noinclude&gt;</text>
    <sha1>58b88ddc94c40339f599638719179f4058670e35</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Documentation</title>
  <ns>10</ns>
  <id>84</id>
  <revision>
    <id>264</id>
    <parentid>222</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="182" xml:space="preserve">{{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}&lt;noinclude&gt;
&lt;!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --&gt;
&lt;/noinclude&gt;</text>
    <sha1>ce7fd93f18c46b4fa871bf679afd05cbda72d8c4</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Collapse bottom</title>
  <ns>10</ns>
  <id>111</id>
  <revision>
    <id>266</id>
    <parentid>265</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">|}&lt;/div&gt;&lt;noinclude&gt;
{{TNT|Documentation}}
&lt;!-- PLEASE ADD THIS TEMPLATE'S CATEGORIES AND INTERWIKIS TO THE /doc SUBPAGE, THANKS --&gt;
&lt;/noinclude&gt;</text>
    <sha1>3e150427ef410d88db3ed21c0539f3e90ee3faab</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Para</title>
  <ns>10</ns>
  <id>112</id>
  <revision>
    <id>268</id>
    <parentid>267</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="267" xml:space="preserve">&lt;code class="nowrap" {{#if:{{{plain|}}}|style="border:none;background-color:inherit;color:inherit;"}}&gt;&amp;#124;{{#if:{{{1|}}}|{{{1}}}&amp;#61;}}{{{2|}}}&lt;/code&gt;&lt;noinclude&gt;
{{Documentation}}
&lt;!--Categories and interwikis go near the bottom of the /doc subpage.--&gt;
&lt;/noinclude&gt;</text>
    <sha1>66770157bb51b0aabb5b874e4f1bb8f04c80915c</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Pagelist</title>
  <ns>10</ns>
  <id>113</id>
  <revision>
    <id>270</id>
    <parentid>269</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4792" xml:space="preserve">&lt;includeonly&gt;{{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{1}}}}}|{{{1}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{1}}}}}|{{{1}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{2|}}}|{{#if:{{{3|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{2}}}}}|{{{2}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{2}}}}}|{{{2}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{3|}}}|{{#if:{{{4|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{3}}}}}|{{{3}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{3}}}}}|{{{3}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{4|}}}|{{#if:{{{5|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{4}}}}}|{{{4}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{4}}}}}|{{{4}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{5|}}}|{{#if:{{{6|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{5}}}}}|{{{5}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{5}}}}}|{{{5}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{6|}}}|{{#if:{{{7|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{6}}}}}|{{{6}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{6}}}}}|{{{6}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{7|}}}|{{#if:{{{8|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{7}}}}}|{{{7}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{7}}}}}|{{{7}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{8|}}}|{{#if:{{{9|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{8}}}}}|{{{8}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{8}}}}}|{{{8}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{9|}}}|{{#if:{{{10|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{9}}}}}|{{{9}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{9}}}}}|{{{9}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{10|}}}|{{#if:{{{11|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{10}}}}}|{{{10}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{10}}}}}|{{{10}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{11|}}}|{{#if:{{{12|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{11}}}}}|{{{11}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{11}}}}}|{{{11}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{12|}}}|{{#if:{{{13|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{12}}}}}|{{{12}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{12}}}}}|{{{12}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{13|}}}|{{#if:{{{14|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{13}}}}}|{{{13}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{13}}}}}|{{{13}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{14|}}}|{{#if:{{{15|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{14}}}}}|{{{14}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{14}}}}}|{{{14}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{15|}}}|{{#if:{{{16|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{15}}}}}|{{{15}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{15}}}}}|{{{15}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{16|}}}|{{#if:{{{17|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{16}}}}}|{{{16}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{16}}}}}|{{{16}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{17|}}}|{{#if:{{{18|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{17}}}}}|{{{17}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{17}}}}}|{{{17}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{18|}}}|{{#if:{{{19|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{18}}}}}|{{{18}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{18}}}}}|{{{18}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{19|}}}|{{#if:{{{20|}}}|,|&lt;nowiki&gt; &lt;/nowiki&gt;and}} {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{19}}}}}|{{{19}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{19}}}}}|{{{19}}}]]}}{{{edelim|{{{delim|}}}}}}&lt;!--
--&gt;{{#if:{{{20|}}}|&lt;nowiki&gt; &lt;/nowiki&gt;and {{{delim|}}}{{#ifeq:{{{nspace|}}}|default|[[:{{FULLPAGENAME:{{{20}}}}}|{{{20}}}]]|[[:{{{nspace|{{NAMESPACE}}}}}:{{PAGENAME:{{{20}}}}}|{{{20}}}]]}}{{{edelim|{{{delim|}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}&lt;!--
--&gt;&lt;/includeonly&gt;&lt;noinclude&gt;
{{documentation}}
&lt;!-- PLEASE ADD CATEGORIES AND INTERWIKIS TO THE /doc SUBPAGE, THANKS --&gt;
&lt;/noinclude&gt;</text>
    <sha1>b956a9df1246a29c44995c86ca9daee3c4830035</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Dummytab</title>
  <ns>10</ns>
  <id>114</id>
  <revision>
    <id>272</id>
    <parentid>271</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="451" xml:space="preserve">&lt;noinclude&gt;&lt;table&gt;&lt;tr&gt;&lt;/noinclude&gt;&lt;td style="width: {{#if:{{{tab spacing percent|}}}|{{#expr:{{{tab spacing percent}}}/2}}|1}}%; border-bottom: {{#if:{{{border|}}}|{{{border}}}|solid 1px #A3B1BF}}"&gt;{{#if:{{{tab spacing percent|}}}||&amp;nbsp;}}&lt;/td&gt;&lt;noinclude&gt;&lt;/tr&gt;&lt;/table&gt;{{doc|content=

This template is used with {{tl|start tab}} to offset the first and last tabs from the end of the tab bar slightly.

[[Category:Formatting templates]]

}}&lt;/noinclude&gt;</text>
    <sha1>3bda72d47644a9d5c168c612904ba7fd70a1650b</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Cartella</title>
  <ns>10</ns>
  <id>115</id>
  <revision>
    <id>274</id>
    <parentid>273</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2490" xml:space="preserve">{| style="width:100%; margin-bottom:.5em; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"
&lt;!-- 1 --&gt;
| rowspan="2" nowrap="nowrap" width="1%" height="37px" valign="top" style="background:#FFF; border:2px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|ABCDEF}}; border-bottom:0; padding:0; padding-right:1em; margin:0; {{border-radius|0 1em 0 0}}" | [[File:cartella_{{#switch:{{{1|}}}|blu=blu|grigio=grigia|verde=verde|viola=viola|arancione=arancione|rosso=rossa|blu}}.jpg|link=|Background]] &lt;div style="margin-top:-31px; padding-left:12px"&gt;[[File:{{{logo|Nuvola apps kalzium.svg}}}|{{{px|22}}}px]]&lt;/div&gt;&lt;div style="padding-left:43px; margin-top:-{{{heightpx|{{#expr:{{{px|22}}} + 4}}}}}px; font-size:130%"&gt;'''{{{titolo}}}'''&lt;/div&gt;
&lt;!-- 2 --&gt;
| height="10px" |
|-
&lt;!-- 3 --&gt;
| class="plainlinks" valign="bottom" style="border-bottom:2px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|ABCDEF}}; text-align:center"| {{#if:{{{link|}}}|&lt;div style="float:left; padding:0 .5em 0 .5em; {{border-radius|0 5em 0 0}} border:1px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|ABCDEF}}; border-left:0; border-bottom:0; background:#{{#switch:{{{1|}}}|blu=ECF5FF|grigio=E3E3E3|verde=CEF2E0|viola=EAEAFF|arancione=FFE9D2|rosso=FFD1D1|ECF5FF}}; font-size:85%"&gt; [{{fullurl:{{{link}}}|action=edit}} edit]|&lt;div style="width:100%;"&gt;&amp;nbsp;&lt;/div&gt;}}
&lt;/div&gt;
|-
&lt;!-- 4 --&gt;
| colspan="2" style="padding-left:.5em; padding-right:.5em; background:#FFF; border:2px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|ABCDEF}}; border-top:0; border-bottom:0" |
{{{contenuto}}}
|-
&lt;!-- 5 --&gt;
| colspan="2" class="radius_bottom" style="background:#{{#switch:{{{1|}}}|blu=ECF5FF|grigio=E3E3E3|verde=CEF2E0|viola=EAEAFF|arancione=FFE9D2|rosso=FFD1D1|FFE9D2}}; height:8px; border:1px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|FFBC79}}; border-right:2px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|FFBC79}}; border-left:2px solid #{{#switch:{{{1|}}}|blu=ABCDEF|grigio=CCC|verde=A3BFB1|viola=C2D3FC|arancione=FFBC79|rosso=F26C6C|FFBC79}}" | &lt;div style="font-size:0"&gt;[[File:pix.gif|1px]]&lt;/div&gt;
|}&lt;noinclude&gt;
{{Documentation}}&lt;/noinclude&gt;</text>
    <sha1>cbf5ed0933ca88b3af094b63574c28917ef468c0</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Start tab</title>
  <ns>10</ns>
  <id>116</id>
  <revision>
    <id>276</id>
    <parentid>275</parentid>
    <timestamp>2016-01-06T06:55:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15216" xml:space="preserve">&lt;includeonly&gt;&lt;!--
  --&gt;&lt;table width="100%" cellspacing=0 cellpadding=0 valign="top" border=0 style="background-color: transparent"&gt;&lt;!--
    --&gt;&lt;tr&gt;&lt;!--
--&gt;{{dummytab|border={{{border|}}}|tab spacing percent={{{tab spacing percent|}}}}}&lt;!--


--&gt;{{#if:{{{tab-1|}}}|{{tab|freeform={{{freeform-1|}}}|link={{{link-1}}}|link2={{{link2-1}}}|link3={{{link3-1}}}|link4={{{link4-1}}}|link5={{{link5-1}}}|tab={{{tab-1}}}|image={{{image-1|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-1|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}|preums=1}}}}&lt;!--


--&gt;{{#if:{{{tab-2|}}}|{{tab|freeform={{{freeform-2|}}}|link={{{link-2}}}|link2={{{link2-2}}}|link3={{{link3-2}}}|link4={{{link4-2}}}|link5={{{link5-2}}}|tab={{{tab-2}}}|image={{{image-2|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-2|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-3|}}}|{{tab|freeform={{{freeform-3|}}}|link={{{link-3}}}|link2={{{link2-3}}}|link3={{{link3-3}}}|link4={{{link4-3}}}|link5={{{link5-3}}}|tab={{{tab-3}}}|image={{{image-3|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-3|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-4|}}}|{{tab|freeform={{{freeform-4|}}}|link={{{link-4}}}|link2={{{link2-4}}}|link3={{{link3-4}}}|link4={{{link4-4}}}|link5={{{link5-4}}}|tab={{{tab-4}}}|image={{{image-4|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-4|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-5|}}}|{{tab|freeform={{{freeform-5|}}}|link={{{link-5}}}|link2={{{link2-5}}}|link3={{{link3-5}}}|link4={{{link4-5}}}|link5={{{link5-5}}}|tab={{{tab-5}}}|image={{{image-5|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-5|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-6|}}}|{{tab|freeform={{{freeform-6|}}}|link={{{link-6}}}|link2={{{link2-6}}}|link3={{{link3-6}}}|link4={{{link4-6}}}|link5={{{link5-6}}}|tab={{{tab-6}}}|image={{{image-6|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-6|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-7|}}}|{{tab|freeform={{{freeform-7|}}}|link={{{link-7}}}|link2={{{link2-7}}}|link3={{{link3-7}}}|link4={{{link4-7}}}|link5={{{link5-7}}}|tab={{{tab-7}}}|image={{{image-7|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-7|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-8|}}}|{{tab|freeform={{{freeform-8|}}}|link={{{link-8}}}|link2={{{link2-8}}}|link3={{{link3-8}}}|link4={{{link4-8}}}|link5={{{link5-8}}}|tab={{{tab-8}}}|image={{{image-8|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-8|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-9|}}}|{{tab|freeform={{{freeform-9|}}}|link={{{link-9}}}|link2={{{link2-9}}}|link3={{{link3-9}}}|link4={{{link4-9}}}|link5={{{link5-9}}}|tab={{{tab-9}}}|image={{{image-9|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-9|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-10|}}}|{{tab|freeform={{{freeform-10|}}}|link={{{link-10}}}|link2={{{link2-10}}}|link3={{{link3-10}}}|link4={{{link4-10}}}|link5={{{link5-10}}}|tab={{{tab-10}}}|image={{{image-10|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-10|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-11|}}}|{{tab|freeform={{{freeform-11|}}}|link={{{link-11}}}|link2={{{link2-11}}}|link3={{{link3-11}}}|link4={{{link4-11}}}|link5={{{link5-11}}}|tab={{{tab-11}}}|image={{{image-11|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-1|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-12|}}}|{{tab|freeform={{{freeform-12|}}}|link={{{link-12}}}|link2={{{link2-12}}}|link3={{{link3-12}}}|link4={{{link4-12}}}|link5={{{link5-12}}}|tab={{{tab-12}}}|image={{{image-12|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-2|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-13|}}}|{{tab|freeform={{{freeform-13|}}}|link={{{link-13}}}|link2={{{link2-13}}}|link3={{{link3-13}}}|link4={{{link4-13}}}|link5={{{link5-13}}}|tab={{{tab-13}}}|image={{{image-13|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-3|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-14|}}}|{{tab|freeform={{{freeform-14|}}}|link={{{link-14}}}|link2={{{link2-14}}}|link3={{{link3-14}}}|link4={{{link4-14}}}|link5={{{link5-14}}}|tab={{{tab-14}}}|image={{{image-14|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-4|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-15|}}}|{{tab|freeform={{{freeform-15|}}}|link={{{link-15}}}|link2={{{link2-15}}}|link3={{{link3-15}}}|link4={{{link4-15}}}|link5={{{link5-15}}}|tab={{{tab-15}}}|image={{{image-15|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-5|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-16|}}}|{{tab|freeform={{{freeform-16|}}}|link={{{link-16}}}|link2={{{link2-16}}}|link3={{{link3-16}}}|link4={{{link4-16}}}|link5={{{link5-16}}}|tab={{{tab-16}}}|image={{{image-16|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-6|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-17|}}}|{{tab|freeform={{{freeform-17|}}}|link={{{link-17}}}|link2={{{link2-17}}}|link3={{{link3-17}}}|link4={{{link4-17}}}|link5={{{link5-17}}}|tab={{{tab-17}}}|image={{{image-17|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-7|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-18|}}}|{{tab|freeform={{{freeform-18|}}}|link={{{link-18}}}|link2={{{link2-18}}}|link3={{{link3-18}}}|link4={{{link4-18}}}|link5={{{link5-18}}}|tab={{{tab-18}}}|image={{{image-18|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-8|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-19|}}}|{{tab|freeform={{{freeform-19|}}}|link={{{link-19}}}|link2={{{link2-19}}}|link3={{{link3-19}}}|link4={{{link4-19}}}|link5={{{link5-19}}}|tab={{{tab-19}}}|image={{{image-19|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-9|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{#if:{{{tab-20|}}}|{{tab|freeform={{{freeform-20|}}}|link={{{link-20}}}|link2={{{link2-20}}}|link3={{{link3-20}}}|link4={{{link4-20}}}|link5={{{link5-20}}}|tab={{{tab-20}}}|image={{{image-20|}}}|{{{tab-1}}}|{{{tab-2}}}|{{{tab-3}}}|{{{tab-4}}}|{{{tab-5}}}|{{{tab-6}}}|{{{tab-7}}}|{{{tab-8}}}|{{{tab-9}}}|{{{tab-10}}}|{{{tab-11}}}|{{{tab-12}}}|{{{tab-13}}}|{{{tab-14}}}|{{{tab-15}}}|{{{tab-16}}}|{{{tab-17}}}|{{{tab-18}}}|{{{tab-19}}}|{{{tab-20}}}|rounding={{{rounding|}}}|border={{{border|}}}|off tab color={{{off tab color-10|{{{off tab color|}}}}}}|on tab color={{{on tab color|}}}|tab spacing percent={{{tab spacing percent|}}}|font-size={{{tab font-size|}}}|tab alignment={{{tab alignment|}}}|nowrap={{{nowrap|}}}}}}}&lt;!--


--&gt;{{dummytab|border={{{border|}}}|tab spacing percent={{{tab spacing percent|}}}}}&lt;!--
--&gt;&lt;/tr&gt;&lt;!--
 --&gt;&lt;/table&gt;&lt;!--
 --&gt;{{#ifeq:{{{frame|}}}|yes|&lt;div style="border: {{{border|solid 1px #a3b1bf}}}; padding: .5em 1em 1em 1em; border-top: none; background-color: {{{frame color|{{{on tab color|transparent}}}}}}; color: black; zoom: 1"&gt;&lt;!--
   --&gt;&lt;div style="padding: 1ex"&gt;}}&lt;!--
--&gt;&lt;/includeonly&gt;&lt;!--
--&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>e76d923db135374f739db247717039ec4e689162</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:End tab</title>
  <ns>10</ns>
  <id>117</id>
  <revision>
    <id>278</id>
    <parentid>277</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1590" xml:space="preserve">&lt;div&gt;&lt;includeonly&gt;&lt;!--

--&gt;{{clear}}&lt;/div&gt;&lt;!--
--&gt;{{#if:{{{URL-1|}}}|&lt;div style="float:right; margin-top: 0.0em; margin-bottom:3px; background-color: {{{Off tab color|#cee0f2}}}; padding: .2em .6em; font-size: 130%; border: {{{border|1px solid #a3b1bf}}}; {{#if:{{{rounding|}}}|-moz-border-radius: {{{rounding}}} {{{rounding}}} 0 0; border-radius: {{{rounding}}} {{{rounding}}} 0 0;}}"&gt; Next page : {{#switch:{{FULLPAGENAME}}|
{{{URL-1}}}=[[{{{URL-2|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-2|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-2}}}=[[{{{URL-3|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-3|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-3}}}=[[{{{URL-4|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-4|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-4}}}=[[{{{URL-5|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-5|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-5}}}=[[{{{URL-6|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-6|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-6}}}=[[{{{URL-7|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-7|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-7}}}=[[{{{URL-8|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-8|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-8}}}=[[{{{URL-9|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-9|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-9}}}=[[{{{URL-10|{{{URL-End|{{{URL-1}}}}}}}}}|'''{{{Tab-10|{{{Tab-End|{{{Tab-1}}}}}}}}}''']]|
{{{URL-10}}}=[[{{{URL-End|{{{URL-1}}}}}}|'''{{{Tab-End|{{{Tab-1}}}}}}''']]|
}}&lt;span style="font-size: larger; font-weight: bold;"&gt;&amp;rarr;&lt;/span&gt;&lt;!--
--&gt;&lt;div style="clear:both"&gt;&lt;/div&gt;&lt;/div&gt;|&lt;div style="clear:both"&gt;&lt;/div&gt;}}&lt;/div&gt;&lt;/includeonly&gt;&lt;noinclude&gt;{{doc}}&lt;/noinclude&gt;</text>
    <sha1>d76a781f167cc46cbbe3bf964b551218821e865e</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Tab</title>
  <ns>10</ns>
  <id>118</id>
  <revision>
    <id>280</id>
    <parentid>279</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1376" xml:space="preserve">&lt;includeonly&gt;{{#if:{{{preums|}}}||&lt;td style="width: {{#if:{{{tab spacing percent|}}}|{{{tab spacing percent}}}|2}}%; border-bottom: {{#if:{{{border|}}}|{{{border}}}|solid 1px #a3b1bf}}"&gt;{{#if:{{{tab spacing percent|}}}||&amp;nbsp;}}&lt;/td&gt;}}&lt;td style="text-align: {{#if:{{{tab alignment|}}}|{{{tab alignment}}}|center}}; {{#if:{{{rounding|}}}|{{border-radius|{{{rounding}}} {{{rounding}}} 0 0}}}} padding:0.3em; border: {{#if:{{{border|}}}|{{{border}}}|solid 1px #a3b1bf}}; font-size: {{#if:{{{font-size|}}}|{{{font-size}}}|110%}}; {{#switch:{{FULLPAGENAME}}|{{{link}}}|{{{link2}}}|{{{link3}}}|{{{link4}}}|{{{link5}}}=background-color: {{#if:{{{on tab color|}}}|{{{on tab color}}}|transparent}}; border-bottom: none; font-weight:bold; |#default=background-color: {{#if:{{{off tab color|}}}|{{{off tab color}}}|#CEE0F2}}; }} {{#ifeq:{{lc:{{{nowrap|}}}}}|yes|white-space: nowrap;}}" width="{{#expr:(100/{{Number of defined parameters|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|{{{5}}}|{{{6}}}|{{{7}}}|{{{8}}}|{{{9}}}|{{{10}}}|{{{11}}}|{{{12}}}|{{{13}}}|{{{14}}}|{{{15}}}|{{{16}}}|{{{17}}}|{{{18}}}|{{{19}}}|{{{20}}}}})-{{#if:{{{tab spacing percent|}}}|{{{tab spacing percent}}}|2}}}}%"&gt;{{#if:{{{image|}}}|[[file:{{{image}}}|20px|{{{tab}}}|link={{{link|}}}]]&amp;nbsp;}}{{#ifeq:{{lc:{{{freeform|}}}}}|yes|{{{tab}}}|[[{{{link}}}|{{{tab}}}]]}}&lt;/td&gt;&lt;/includeonly&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>d7e78c5489777e489ec4a0320f35ec9c30b7c32e</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:CompactTOC8</title>
  <ns>10</ns>
  <id>119</id>
  <revision>
    <id>282</id>
    <parentid>281</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8428" xml:space="preserve">{|&lt;!--=======================================================
    --  Template CompactTOC8 -  (see NOTES at bottom)
    --=======================================================
--
--&gt; id="toc" class="toc" summary="Contents" {{
&lt;!-- ----------------------------------- Check center/right--&gt;
#ifeq:{{{center|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|align="center"|}}{{#ifeq:{{{right|}}}|yes|align="right"|}}
{{       &lt;!--see NOTE I3 below--&gt;
&lt;!-- ----------------------------------- Check name/side--&gt;
#ifeq:{{{name|}}}|no||! {{{name|{{MediaWiki:Toc}}}}}{{#ifeq:{{{side|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|&amp;#58;|}}
{{#ifeq:{{{side|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|{{!}}|{{!}}-}}}}
|{{#ifeq:{{{nobreak|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes||&lt;div style="text-align:{{{align|left}}};"&gt;}}{{
&lt;!-- --------------------------------------- Check top --&gt;
#ifeq:{{{top|}}}|yes|[[#top{{!}}Top]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
&lt;!-- --------------------------------------- Prefix headers--
          (see NOTE P2 below) --&gt;
#if:{{{pre1|{{{preSec1|}}}}}}|[[{{{pre1link|{{{preSec1link|#{{{pre1|{{{preSec1|}}}}}}}}}}}}{{!}}{{{pre1name|{{{preSec1name|{{{pre1|{{{preSec1|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre2|{{{preSec2|}}}}}}|[[{{{pre2link|{{{preSec2link|#{{{pre2|{{{preSec2|}}}}}}}}}}}}{{!}}{{{pre2name|{{{preSec2name|{{{pre2|{{{preSec2|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre3|{{{preSec3|}}}}}}|[[{{{pre3link|{{{preSec3link|#{{{pre3|{{{preSec3|}}}}}}}}}}}}{{!}}{{{pre3name|{{{preSec3name|{{{pre3|{{{preSec3|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre4|{{{preSec4|}}}}}}|[[{{{pre4link|{{{preSec4link|#{{{pre4|{{{preSec4|}}}}}}}}}}}}{{!}}{{{pre4name|{{{preSec4name|{{{pre4|{{{preSec4|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre5|{{{preSec5|}}}}}}|[[{{{pre5link|{{{preSec5link|#{{{pre5|{{{preSec5|}}}}}}}}}}}}{{!}}{{{pre5name|{{{preSec5name|{{{pre5|{{{preSec5|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre6|{{{preSec6|}}}}}}|[[{{{pre6link|{{{preSec6link|#{{{pre6|{{{preSec6|}}}}}}}}}}}}{{!}}{{{pre6name|{{{preSec6name|{{{pre6|{{{preSec6|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre7|{{{preSec7|}}}}}}|[[{{{pre7link|{{{preSec7link|#{{{pre7|{{{preSec7|}}}}}}}}}}}}{{!}}{{{pre7name|{{{preSec7name|{{{pre7|{{{preSec7|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
#if:{{{pre8|{{{preSec8|}}}}}}|[[{{{pre8link|{{{preSec8link|#{{{pre8|{{{preSec8|}}}}}}}}}}}}{{!}}{{{pre8name|{{{preSec8name|{{{pre8|{{{preSec8|}}}}}}}}}}}}]]&amp;nbsp;{{{sep|&amp;nbsp;}}}|}} {{
&lt;!-- --------------------------------------- Check prebreak--&gt;
#if:{{{prebreak|}}}|{{{prebreak}}}}} {{
&lt;!-- --------------------------------------- Check symbols --&gt;
#ifeq:{{{sym|}}}|yes|[[#!$@|!$@]]|}} {{
&lt;!-- --------------------------------------- Check numbers --&gt;
#ifeq:{{{num|}}}|yes|[[#0–9|0–9]]|}} {{#ifeq:{{{symnum|}}}|yes|[[#!–9|!–9]]|
&lt;!-- --------------------------------------- List letters --&gt;
}} {{{a|[[#A|A]]}}} {{{b|[[#B|B]]}}} {{{c|[[#C|C]]}}} {{{d|[[#D|D]]}}} {{{e|[[#E|E]]}}} {{{f|[[#F|F]]}}} {{{g|[[#G|G]]}}} {{{h|[[#H|H]]}}} {{{i|[[#I|I]]}}} {{{j|[[#J|J]]}}} {{{k|[[#K|K]]}}} {{{l|[[#L|L]]}}} {{{m|[[#M|M]]}}} {{{n|[[#N|N]]}}} {{{o|[[#O|O]]}}} {{{p|[[#P|P]]}}} {{{q|[[#Q|Q]]}}} {{{r|[[#R|R]]}}} {{{s|[[#S|S]]}}} {{{t|[[#T|T]]}}} {{{u|[[#U|U]]}}} {{{v|[[#V|V]]}}} {{{w|[[#W|W]]}}} {{{x|[[#X|X]]}}} {{{y|[[#Y|Y]]}}} {{{z|[[#Z|Z]]}}} {{#ifeq:{{{nobreak|{{#ifeq:{{{1}}}|short1|yes|}}}}}|yes|&amp;nbsp;|&lt;br /&gt;}}{{
&lt;!-- ------------------------------ Check after-header1 -
          (see NOTE C2 below) --&gt;
#if:{{{custom1|{{{Sec1|}}}}}}|[[{{{custom1link|{{{Sec1link|#{{{custom1|{{{Sec1|}}}}}}}}}}}}{{!}}{{{custom1name|{{{Sec1name|{{{custom1|{{{Sec1|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
&lt;!-- ------------------------------ Check after-header2...--&gt;
#if:{{{custom2|{{{Sec2|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom2link|{{{Sec2link|#{{{custom2|{{{Sec2|}}}}}}}}}}}}{{!}}{{{custom2name|{{{Sec2name|{{{custom2|{{{Sec2|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom3|{{{Sec3|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom3link|{{{Sec3link|#{{{custom3|{{{Sec3|}}}}}}}}}}}}{{!}}{{{custom3name|{{{Sec3name|{{{custom3|{{{Sec3|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom4|{{{Sec4|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom4link|{{{Sec4link|#{{{custom4|{{{Sec4|}}}}}}}}}}}}{{!}}{{{custom4name|{{{Sec4name|{{{custom4|{{{Sec4|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom5|{{{Sec5|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom5link|{{{Sec5link|#{{{custom5|{{{Sec5|}}}}}}}}}}}}{{!}}{{{custom5name|{{{Sec5name|{{{custom5|{{{Sec5|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom6|{{{Sec6|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom6link|{{{Sec6link|#{{{custom6|{{{Sec6|}}}}}}}}}}}}{{!}}{{{custom6name|{{{Sec6name|{{{custom6|{{{Sec6|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom7|{{{Sec7|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom7link|{{{Sec7link|#{{{custom7|{{{Sec7|}}}}}}}}}}}}{{!}}{{{custom7name|{{{Sec7name|{{{custom7|{{{Sec7|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
#if:{{{custom8|{{{Sec8|}}}}}}|{{{sep|&amp;nbsp;}}} [[{{{custom8link|{{{Sec8link|#{{{custom8|{{{Sec8|}}}}}}}}}}}}{{!}}{{{custom8name|{{{Sec8name|{{{custom8|{{{Sec8|}}}}}}}}}}}}]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Check seealso--&gt;
#ifeq:{{{seealso|}}}|yes|{{{sep|&amp;nbsp;}}} [[#See also{{!}}See also]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Check notesfirst--&gt;
#ifeq:{{{notesfirst|}}}|yes|{{{sep|&amp;nbsp;}}} [[#Notes{{!}}Notes]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Check refs--&gt;
#ifeq:{{{refs|{{#ifeq:{{{1|}}}|short1|yes|}}}}}|yes|{{{sep|&amp;nbsp;}}} [[#References{{!}}References]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Check notes--&gt;
#ifeq:{{{notes|}}}|yes|{{{sep|&amp;nbsp;}}} [[#Notes{{!}}Notes]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Further reading--&gt;
#ifeq:{{{further|}}}|yes|{{{sep|&amp;nbsp;}}} [[#Further reading{{!}}Further reading]]&amp;nbsp;|}}{{
&lt;!-- ---------------------------------- Check extlinks--&gt;
#ifeq:{{{extlinks|}}}|yes|{{{sep|&amp;nbsp;}}} [[#External links{{!}}External links]]|}}{{
&lt;!-- ================================== Check invalid words--&gt;
#ifeq:{{{break|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "break" - try "nobreak=yes".
}}{{#ifeq:{{{centre|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "centre" - try "center=yes".
}}{{#ifeq:{{{Top|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "Top" - try lowercase "top=yes".
}}{{#ifeq:{{{ref|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "ref" - try "refs=yes".
}}{{#ifeq:{{{Ref|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "Ref" - try lowercase "refs=yes".
}}{{#ifeq:{{{note|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "note" - try "note'''s'''=yes".
}}{{#ifeq:{{{ext|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "ext" - try "extlinks=yes".
}}{{#ifeq:{{{extlink|x}}}|x||&lt;br&gt;
  TOC8 - Invalid parameter "extlink" - try "extlinks=yes".
}}&lt;/div&gt;
|}__NOTOC__&lt;noinclude&gt;

{{documentation}}
&lt;!--PLEASE ADD CATEGORIES &amp; INTERWIKIS TO /doc PAGE, THANKS--&gt;
&lt;!--
--       -------------------------------------------------
--NOTES:
--
-- NOTE C2: Parameter "custom1=zzz" or "Sec1=zzz" shows first
--          subheader "zzz" after the "0-9 A B C D...".
--
-- NOTE I3: If-statements can be indented by leaving "{{" at
--          end of previous line and put "#if:" on next line;
--          otherwise indented lines become quote-boxes.
--
-- NOTE P2: Parameter "pre1=xxx" shows first subheader "xxx"
--          before the condensed "0-9 A B C..." appears.
--
-- NOTE S2: Parameter "sep=&amp;middot;" defines the separator
--          string displayed between subheaders (not letters).
--          It defaults to a single space, "sep=&amp;nbsp;".
--
-- NOTE V9: Coded for MediaWiki language 1.11.1 (Jan.2008);
--          wiki-format now omits HTML comments on web xfer.
--HISTORY:
-- 10Jan09 Added parameters: sep=&amp;middot; and prebreak=&lt;br&gt;.
-- 10Jan09 Added parameters: 3 more custom6, custom7, custom8.
-- 10Jan09 Added parameters: 3 more custom6link...custom8link.
-- 10Jan09 Added parameters: 3 more custom6name...custom8name.
-- 10Jan09 Added parameters: pre1, pre2, pre3... pre7, pre8.
-- 10Jan09 Added parameters: pre1link, pre2link ... pre8link.
-- 10Jan09 Added parameters: pre1name, pre2name ... pre8name.
-- 10Jan09 Added parameters: preSec1, preSec2, ... preSec8.
-- 10Jan09 Spot invalid keywords: Top/ref/Ref/note/ext etc.
-- 10Jan09 Added NOTES comments to explain template coding.
-- 10Jan09 Added HISTORY comments to log major changes.
-- 01Jul11 Added Further reading
-- [These comment lines are omitted before Internet transfer.]
--
--End Template:CompactTOC8--&gt;
{{Languages}}
&lt;/noinclude&gt;</text>
    <sha1>19bf5d824ad4f112de95d6e7d3418e8e479dec71</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Rellink</title>
  <ns>10</ns>
  <id>120</id>
  <revision>
    <id>284</id>
    <parentid>283</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155" xml:space="preserve">&lt;div class="rellink mw-tpl-rellink{{#if:{{{extraclasses|}}}|&lt;nowiki&gt; &lt;/nowiki&gt;{{{extraclasses}}}}}"&gt;{{{1}}}&lt;/div&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>eb9f18d0972fa390e07dd7bbb6db1cd7ac44d352</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Navbox</title>
  <ns>10</ns>
  <id>121</id>
  <revision>
    <id>286</id>
    <parentid>285</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="94" xml:space="preserve">&lt;includeonly&gt;{{#invoke:Navbox|navbox}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>fe9b964401f895918ee4fe078678f1722a3c41ec</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Navbar</title>
  <ns>10</ns>
  <id>99</id>
  <revision>
    <id>288</id>
    <parentid>240</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1087" xml:space="preserve">&lt;span class="noprint plainlinks navbar" style="{{{style|}}}"&gt;&lt;small&gt;&lt;!--

--&gt;{{#if:{{{mini|}}}{{{plain|}}}|&lt;!--nothing--&gt;|&lt;!--else:
--&gt;&lt;span style="{{{fontstyle|}}}"&gt;{{{text|This box:}}} &lt;/span&gt;}}&lt;!--

--&gt;{{#if:{{{brackets|}}}|&lt;span style="{{{fontstyle|}}}"&gt;&amp;#91;&lt;/span&gt;}}&lt;!--

--&gt;&lt;span style="white-space:nowrap;word-spacing:-.12em;"&gt;&lt;!--
--&gt;[[{{ns:10}}:{{{1}}}|&lt;span style="{{{fontstyle|}}}" title="View this template"&gt;&lt;!--
--&gt;{{#if:{{{mini|}}}|v|view}}&lt;/span&gt;]]&lt;!--

--&gt;&lt;span style="{{{fontstyle|}}}"&gt;&amp;#32;&lt;b&gt;&amp;middot;&lt;/b&gt;&amp;#32;&lt;/span&gt;&lt;!--
--&gt;[[{{ns:11}}:{{{1}}}|&lt;span style="{{{fontstyle|}}}" title="Discuss this template"&gt;&lt;!--
--&gt;{{#if:{{{mini|}}}|d|talk}}&lt;/span&gt;]]&lt;!--

--&gt;{{#if:{{{noedit|}}}|&lt;!--nothing--&gt;|&lt;!--else:
--&gt;&lt;span style="{{{fontstyle|}}}"&gt;&amp;#32;&lt;b&gt;&amp;middot;&lt;/b&gt;&amp;#32;&lt;/span&gt;&lt;!--
--&gt;[{{fullurl:{{ns:10}}:{{{1}}}|action=edit}} &lt;span style="{{{fontstyle|}}}" title="Edit this template"&gt;&lt;!--
--&gt;{{#if:{{{mini|}}}|e|edit}}&lt;/span&gt;]}}&lt;!--
--&gt;&lt;/span&gt;&lt;!--

--&gt;{{#if:{{{brackets|}}}|&lt;span style="{{{fontstyle|}}}"&gt;&amp;#93;&lt;/span&gt;}}&lt;!--

--&gt;&lt;/small&gt;&lt;/span&gt;
&lt;noinclude&gt;{{doc}}&lt;/noinclude&gt;</text>
    <sha1>08cf4451d76bbca3ac4337d6976839bb230b2c9a</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Transclude</title>
  <ns>10</ns>
  <id>122</id>
  <revision>
    <id>290</id>
    <parentid>289</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="400" xml:space="preserve">{{#switch: {{NAMESPACE: {{{1}}} }}
 |#default = {{FULLPAGENAME: {{{1}}} }} &lt;!-- eg "User:Foo" --&gt;
 |{{ns:0}} = 
    {{#ifeq: {{NAMESPACE: {{{1}}} }} | {{NAMESPACE: Template{{{1}}} }}
      | Template:{{{1}}}            &lt;!-- no leading colon, eg "Foo" --&gt;
      | {{PAGENAME: {{{1}}} }}      &lt;!-- leading colon, eg ":Foo", so we want the article --&gt;
    }}
}}&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>d0239e71e5745cd0d4efd032cee07341e111376b</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Magnify icon</title>
  <ns>10</ns>
  <id>123</id>
  <revision>
    <id>292</id>
    <parentid>291</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="131" xml:space="preserve">&lt;div class="magnify"&gt;[[File:Magnify-clip.png|15x13px|link={{{link}}}|alt=|Enlarge]]&lt;/div&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>ec1af95c57fa159203d3904a66a4890f70f4791b</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Documentation/sandbox</title>
  <ns>10</ns>
  <id>124</id>
  <revision>
    <id>294</id>
    <parentid>293</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="182" xml:space="preserve">{{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}&lt;noinclude&gt;
&lt;!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --&gt;
&lt;/noinclude&gt;</text>
    <sha1>ce7fd93f18c46b4fa871bf679afd05cbda72d8c4</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Box-round</title>
  <ns>10</ns>
  <id>125</id>
  <revision>
    <id>296</id>
    <parentid>295</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1414" xml:space="preserve">__NOEDITSECTION__ __NOTOC__&lt;div style="clear: both;"&gt;&lt;/div&gt; 
&lt;div style="border: 1px solid {{{border|#99c}}};&lt;!--
         --&gt;background: {{{titlebackground|#ccf}}};&lt;!--
         --&gt;color: {{{titleforeground|#000}}};&lt;!--
         --&gt;padding: .1em;&lt;!--
         --&gt;text-align: center;&lt;!--
         --&gt;font-weight: bold;&lt;!--
         --&gt;font-size: 100%;&lt;!--
         --&gt;margin-bottom: 0px;&lt;!--
         --&gt;border-bottom: none;&lt;!--
         --&gt;{{border-radius|1.5em 1.5em 0 0}}&lt;!--
         --&gt;{{{titlestyle|}}};"&gt;&lt;!--
  --&gt;&lt;span class="plainlinks" &lt;!-- EDIT LINK PARAMETERS
        --&gt;style="float:right;&lt;!--
              --&gt;margin-bottom:.1em;&lt;!--
              --&gt;font-size: 80%;&lt;!--
              --&gt;padding-right: 0.5em;"&gt;&lt;!--
        --&gt;&lt;font color="{{{titleforeground|#000000}}}"&gt;[{{fullurl:{{{editpage|{{FULLPAGENAME}}}}}|action=edit}} {{int:editsection}}]&lt;/font&gt;&amp;nbsp;&lt;!--
  --&gt;&lt;/span &gt;&lt;!--
  --&gt;&lt;h2 style="font-size:100%;font-weight:bold;border: none; margin: 0; padding:0; padding-bottom:.1em;"&gt;&lt;font color="{{{titleforeground|#000000}}}"&gt;{{{title}}}&lt;/font&gt;&lt;/h2&gt;&lt;/div&gt;
&lt;div style="display: block; border: 1px solid {{{border|#99c}}}; vertical-align: top; background: {{{background|#fff}}}; color: {{{foreground|#000}}}; margin-bottom: 10px; padding: .8em 1em 1em 1.3em; margin-top: 0em; {{border-radius|0 0 1.5em 1.5em}} {{{style|}}};"&gt;{{{1|{{{text|{{{content}}}}}}}}}&lt;/div&gt;
&lt;noinclude&gt;{{doc}}&lt;/noinclude&gt;</text>
    <sha1>1dcefd534a80e840f0eeb69bfa4b352fd3d0b1d5</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Tab/sandbox</title>
  <ns>10</ns>
  <id>126</id>
  <revision>
    <id>298</id>
    <parentid>297</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1376" xml:space="preserve">&lt;includeonly&gt;{{#if:{{{preums|}}}||&lt;td style="width: {{#if:{{{tab spacing percent|}}}|{{{tab spacing percent}}}|2}}%; border-bottom: {{#if:{{{border|}}}|{{{border}}}|solid 1px #a3b1bf}}"&gt;{{#if:{{{tab spacing percent|}}}||&amp;nbsp;}}&lt;/td&gt;}}&lt;td style="text-align: {{#if:{{{tab alignment|}}}|{{{tab alignment}}}|center}}; {{#if:{{{rounding|}}}|{{border-radius|{{{rounding}}} {{{rounding}}} 0 0}}}} padding:0.3em; border: {{#if:{{{border|}}}|{{{border}}}|solid 1px #a3b1bf}}; font-size: {{#if:{{{font-size|}}}|{{{font-size}}}|110%}}; {{#switch:{{FULLPAGENAME}}|{{{link}}}|{{{link2}}}|{{{link3}}}|{{{link4}}}|{{{link5}}}=background-color: {{#if:{{{on tab color|}}}|{{{on tab color}}}|transparent}}; border-bottom: none; font-weight:bold; |#default=background-color: {{#if:{{{off tab color|}}}|{{{off tab color}}}|#CEE0F2}}; }} {{#ifeq:{{lc:{{{nowrap|}}}}}|yes|white-space: nowrap;}}" width="{{#expr:(100/{{Number of defined parameters|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|{{{5}}}|{{{6}}}|{{{7}}}|{{{8}}}|{{{9}}}|{{{10}}}|{{{11}}}|{{{12}}}|{{{13}}}|{{{14}}}|{{{15}}}|{{{16}}}|{{{17}}}|{{{18}}}|{{{19}}}|{{{20}}}}})-{{#if:{{{tab spacing percent|}}}|{{{tab spacing percent}}}|2}}}}%"&gt;{{#if:{{{image|}}}|[[file:{{{image}}}|20px|{{{tab}}}|link={{{link|}}}]]&amp;nbsp;}}{{#ifeq:{{lc:{{{freeform|}}}}}|yes|{{{tab}}}|[[{{{link}}}|{{{tab}}}]]}}&lt;/td&gt;&lt;/includeonly&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>d7e78c5489777e489ec4a0320f35ec9c30b7c32e</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:ApiParam</title>
  <ns>10</ns>
  <id>127</id>
  <revision>
    <id>300</id>
    <parentid>299</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="748" xml:space="preserve">&lt;includeonly&gt;*{{{bullet|}}} &lt;code {{#if:{{{required|}}}|style="font-weight:bold"}}&gt;{{{1|{{{name|}}}}}}&lt;/code&gt;{{#if:{{{2|{{{description|}}}}}}|&amp;#58; {{{2|{{{description|}}}}}}}}{{#if:{{{maxallowed|}}}|&amp;#32;No more than {{{maxallowed}}} ({{{maxallowedbot|{{#switch:{{{maxallowed}}}|50=500|500=5000}}}}} for bots) allowed.}}{{#if:{{{type|}}}|&amp;#32;'''Type''': {{{type}}}}}{{#if:{{{values|}}}|&amp;#32;Possible values: {{{values}}}.}}{{#if:{{{default|}}}|&amp;#32;(Default: {{{default}}})}}{{#if:{{{version|}}}|&amp;#32;{{MW version-inline|{{{version}}}+}}}}{{#if:{{{deprecated|}}}|&amp;#32;{{Deprecated-inline|{{{deprecated}}}}}}}{{#if:{{{removed|}}}|&amp;#32;{{ {{TNTN|Removed-inline}} |{{{removed}}}}}}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{ {{TNTN|Documentation}} }}
&lt;/noinclude&gt;</text>
    <sha1>c3ec38a9643cc68da7d82786a2db6192c709f250</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Smallcaps</title>
  <ns>10</ns>
  <id>128</id>
  <revision>
    <id>302</id>
    <parentid>301</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="120" xml:space="preserve">&lt;includeonly&gt;&lt;span style="font-variant: small-caps"&gt;{{{1}}}&lt;/span&gt;&lt;/includeonly&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>96dbaf71349f4af78c01cfab7eaa8fd953fa7784</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Clear</title>
  <ns>10</ns>
  <id>129</id>
  <revision>
    <id>304</id>
    <parentid>303</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="81" xml:space="preserve">&lt;div style="clear:{{{1|both}}};"&gt;&lt;/div&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>38bab3e3d7fbd3d6800d46556e60bc6bac494d72</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Dir</title>
  <ns>10</ns>
  <id>130</id>
  <revision>
    <id>306</id>
    <parentid>305</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="208" xml:space="preserve">{{#switch:{{lc:{{{1|{{int:lang}}}}}}}|ar|arc|arz|azb|bcc|ckb|bqi|dv|fa|fa-af|glk|ha|he|kk-arab|kk-cn|ks|ku-arab|mzn|pnb|prd|ps|sd|ug|ur|ydd|yi={{{2|rtl}}}|{{{3|ltr}}}}}&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>7d9c312af67f9eff96e7bdfce0f77cb52ca72aea</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:-</title>
  <ns>10</ns>
  <id>131</id>
  <revision>
    <id>308</id>
    <parentid>307</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="76" xml:space="preserve">&lt;br style="clear: {{{1|both}}};" /&gt;&lt;noinclude&gt;
{{Documentation}}&lt;/noinclude&gt;</text>
    <sha1>ff24c103813c340e95b3035eab8f1662c8649747</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Tl</title>
  <ns>10</ns>
  <id>24</id>
  <revision>
    <id>310</id>
    <parentid>24</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="168" xml:space="preserve">&amp;#123;&amp;#123;[[Template:{{{1}}}|{{{1}}}]]&amp;#125;&amp;#125;&lt;noinclude&gt;
{{documentation}}
&lt;!-- Categories go on the /doc subpage and interwikis go on Wikidata. --&gt;
&lt;/noinclude&gt;</text>
    <sha1>91be693cd63410db06fc933eddb412ba433564dc</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Tlx</title>
  <ns>10</ns>
  <id>91</id>
  <revision>
    <id>312</id>
    <parentid>229</parentid>
    <timestamp>2016-01-06T06:55:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="398" xml:space="preserve">{{[[{{#if:{{{SISTER|}}}|{{{SISTER}}}Template|{{ns:Template}}}}:{{{1|Tlx}}}|{{{1|Tlx}}}]]&lt;!--
--&gt;{{#if:{{{2|}}}|&amp;#124;{{{2}}}}}&lt;!--
--&gt;{{#if:{{{3|}}}|&amp;#124;{{{3}}}}}&lt;!--
--&gt;{{#if:{{{4|}}}|&amp;#124;{{{4}}}}}&lt;!--
--&gt;{{#if:{{{5|}}}|&amp;#124;{{{5}}}}}&lt;!--
--&gt;{{#if:{{{6|}}}|&amp;#124;{{{6}}}}}&lt;!--
--&gt;{{#if:{{{7|}}}|&amp;#124;{{{7}}}}}&lt;!--
--&gt;{{#if:{{{8|}}}|&amp;#124;''...''}}}}&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>31fa8846f3adf381b3a4943183ffd00c2489a2ff</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:GetFallback</title>
  <ns>10</ns>
  <id>132</id>
  <revision>
    <id>314</id>
    <parentid>313</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="906" xml:space="preserve">{{#switch: {{Uselang|lang={{{1|}}}}}
| af | fy | li | nl-informal | vls | zea = nl
| arz = ar
| be-tarask = be-x-old
| be-x-old = be-tarask &lt;!-- same language; be-x-old is used on be-x-old.wikipedia but be-tarask is the preferred code --&gt;
| crh-cyrl | crh-latn = crh
| ckb | mzn | glk = fa
| als | bar | de-formal | de-at | de-ch | frr | ksh = de
| hif-deva | hif-latn = hif
| ike-cans | ike-latn = ike
| kk-arab | kk-cyrl | kk-latn | kk-cn | kk-kz | kk-tr = kk
| ku-latn | ku-arab = ku
| mg | br | co | frp | ht | ty | wa = fr
| nds = nds-nl
| nds-nl | pdt = nds
| pt-br = pt
| ruq-cyrl | ruq-grek | ruq-latn = ruq
| sr-ec | sr-el = sr
| tg-cyrl | tg-latn = tg
| tt-cyrl | tt-latn = tt
| vec = it
| zh | zh-cn | zh-my | zh-sg = zh-hans
| zh-hk | zh-mo | zh-tw = zh-hant
| szl | csb = pl
| en-gb = en 
| #default = {{#if: {{{default|}}} | {{{default|}}} | en }}
}}&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>b81791cc126e09f5e9e4c149056a58ba8b929a9d</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:LangSwitch</title>
  <ns>10</ns>
  <id>133</id>
  <revision>
    <id>316</id>
    <parentid>315</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="631" xml:space="preserve">{{{ 
  {{#switch: {{{ {{Uselang|lang={{{lang|}}}}} |}}} 
  | ~ = empty
  |   = {{#switch: {{{ {{GetFallback| {{Uselang|lang={{{lang|}}}}} |default=default}} |}}}
    | ~ = empty
    |   = {{#switch: {{{ {{GetFallback2| {{Uselang|lang={{{lang|}}}}} |default=default}} |}}}
      | ~        = empty
      |          = {{#if: {{{default|}}} | default | en }}
      | #default = {{GetFallback2| {{Uselang|lang={{{lang|}}}}} |default=default}}
      }}
    | #default = {{GetFallback| {{Uselang|lang={{{lang|}}}}} |default=default}}
    }}
  | #default = {{Uselang|lang={{{lang|}}}}}
  }} 
|}}}&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>6276da6db4a231df3efb5b4f4a68cc35dc2b8211</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Languages</title>
  <ns>10</ns>
  <id>134</id>
  <revision>
    <id>318</id>
    <parentid>317</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4965" xml:space="preserve">{{nmbox
 | header = '''[[Project:Language policy|{{Languages/Title|{{SUBPAGENAME}}}}]]'''
 | text = 
'''[[{{{1|:{{NAMESPACE}}:{{BASEPAGENAME}}}}}|English]]''' {{Languages/Lang|af|{{{1|}}}|
}}{{Languages/Lang|ar|{{{1|}}}|
}}{{Languages/Lang|ast|{{{1|}}}|
}}{{Languages/Lang|az|{{{1|}}}|
}}{{Languages/Lang|bcc|{{{1|}}}|
}}{{Languages/Lang|bg|{{{1|}}}|
}}{{Languages/Lang|br|{{{1|}}}|
}}{{Languages/Lang|bn|{{{1|}}}|
}}{{Languages/Lang|bs|{{{1|}}}|
}}{{Languages/Lang|ca|{{{1|}}}|
}}{{Languages/Lang|cs|{{{1|}}}|
}}{{Languages/Lang|da|{{{1|}}}|
}}{{Languages/Lang|de|{{{1|}}}|
}}{{Languages/Lang|diq|{{{1|}}}|
}}{{Languages/Lang|el|{{{1|}}}|
}}{{Languages/Lang|eo|{{{1|}}}|
}}{{Languages/Lang|es|{{{1|}}}|
}}{{Languages/Lang|fa|{{{1|}}}|
}}{{Languages/Lang|fi|{{{1|}}}|
}}{{Languages/Lang|fr|{{{1|}}}|
}}{{Languages/Lang|gl|{{{1|}}}|
}}{{Languages/Lang|gu|{{{1|}}}|
}}{{Languages/Lang|he|{{{1|}}}|
}}{{Languages/Lang|hi|{{{1|}}}|
}}{{Languages/Lang|hu|{{{1|}}}|
}}{{Languages/Lang|hy|{{{1|}}}|
}}{{Languages/Lang|id|{{{1|}}}|
}}{{Languages/Lang|io|{{{1|}}}|
}}{{Languages/Lang|it|{{{1|}}}|
}}{{Languages/Lang|ja|{{{1|}}}|
}}{{Languages/Lang|ka|{{{1|}}}|
}}{{Languages/Lang|kk|{{{1|}}}|
}}&lt;span class="autonym"&gt;{{Languages/Lang|km|{{{1|}}}|
}}&lt;/span&gt;{{Languages/Lang|ko|{{{1|}}}|
}}{{Languages/Lang|ksh|{{{1|}}}|
}}{{Languages/Lang|kw|{{{1|}}}|
}}{{Languages/Lang|la|{{{1|}}}|
}}{{Languages/Lang|min|{{{1|}}}|
}}{{Languages/Lang|mk|{{{1|}}}|
}}{{Languages/Lang|ml|{{{1|}}}|
}}&lt;span class="autonym"&gt;{{Languages/Lang|mr|{{{1|}}}|
}}&lt;/span&gt;{{Languages/Lang|ms|{{{1|}}}|
}}{{Languages/Lang|nl|{{{1|}}}|
}}{{Languages/Lang|no|{{{1|}}}|
}}{{Languages/Lang|oc|{{{1|}}}|
}}{{Languages/Lang|or|{{{1|}}}|
}}{{Languages/Lang|pl|{{{1|}}}|
}}{{Languages/Lang|pt|{{{1|}}}|
}}{{Languages/Lang|pt-br|{{{1|}}}|
}}{{Languages/Lang|ro|{{{1|}}}|
}}{{Languages/Lang|ru|{{{1|}}}|
}}{{Languages/Lang|si|{{{1|}}}|
}}{{Languages/Lang|sk|{{{1|}}}|
}}{{Languages/Lang|sl|{{{1|}}}|
}}{{Languages/Lang|so|{{{1|}}}|
}}{{Languages/Lang|sq|{{{1|}}}|
}}{{Languages/Lang|sr|{{{1|}}}|
}}{{Languages/Lang|sv|{{{1|}}}|
}}{{Languages/Lang|ta|{{{1|}}}|
}}{{Languages/Lang|th|{{{1|}}}|
}}{{Languages/Lang|tr|{{{1|}}}|
}}{{Languages/Lang|uk|{{{1|}}}|
}}{{Languages/Lang|vi|{{{1|}}}|
}}{{Languages/Lang|yi|{{{1|}}}|
}}{{Languages/Lang|yue|{{{1|}}}|
}}{{Languages/Lang|zh|{{{1|}}}|
}}{{Languages/Lang|zh-hans|{{{1|}}}|
}}{{Languages/Lang|zh-hant|{{{1|}}}|
}}{{Languages/Lang|zh-tw|{{{1|}}}}}|
}}&lt;includeonly&gt;{{#if:{{Languages/Lang|af|{{{1|}}}|
}}{{Languages/Lang|ar|{{{1|}}}|
}}{{Languages/Lang|ast|{{{1|}}}|
}}{{Languages/Lang|az|{{{1|}}}|
}}{{Languages/Lang|bcc|{{{1|}}}|
}}{{Languages/Lang|bg|{{{1|}}}|
}}{{Languages/Lang|br|{{{1|}}}|
}}{{Languages/Lang|bn|{{{1|}}}|
}}{{Languages/Lang|bs|{{{1|}}}|
}}{{Languages/Lang|ca|{{{1|}}}|
}}{{Languages/Lang|cs|{{{1|}}}|
}}{{Languages/Lang|da|{{{1|}}}|
}}{{Languages/Lang|de|{{{1|}}}|
}}{{Languages/Lang|diq|{{{1|}}}|
}}{{Languages/Lang|el|{{{1|}}}|
}}{{Languages/Lang|eo|{{{1|}}}|
}}{{Languages/Lang|es|{{{1|}}}|
}}{{Languages/Lang|fa|{{{1|}}}|
}}{{Languages/Lang|fi|{{{1|}}}|
}}{{Languages/Lang|fr|{{{1|}}}|
}}{{Languages/Lang|gl|{{{1|}}}|
}}{{Languages/Lang|gu|{{{1|}}}|
}}{{Languages/Lang|he|{{{1|}}}|
}}{{Languages/Lang|hi|{{{1|}}}|
}}{{Languages/Lang|hu|{{{1|}}}|
}}{{Languages/Lang|hy|{{{1|}}}|
}}{{Languages/Lang|id|{{{1|}}}|
}}{{Languages/Lang|io|{{{1|}}}|
}}{{Languages/Lang|it|{{{1|}}}|
}}{{Languages/Lang|ja|{{{1|}}}|
}}{{Languages/Lang|ka|{{{1|}}}|
}}{{Languages/Lang|kk|{{{1|}}}|
}}{{Languages/Lang|km|{{{1|}}}|
}}{{Languages/Lang|ko|{{{1|}}}|
}}{{Languages/Lang|ksh|{{{1|}}}|
}}{{Languages/Lang|kw|{{{1|}}}|
}}{{Languages/Lang|la|{{{1|}}}|
}}{{Languages/Lang|min|{{{1|}}}|
}}{{Languages/Lang|mk|{{{1|}}}|
}}{{Languages/Lang|ml|{{{1|}}}|
}}{{Languages/Lang|mr|{{{1|}}}|
}}{{Languages/Lang|ms|{{{1|}}}|
}}{{Languages/Lang|nl|{{{1|}}}|
}}{{Languages/Lang|no|{{{1|}}}|
}}{{Languages/Lang|oc|{{{1|}}}|
}}{{Languages/Lang|or|{{{1|}}}|
}}{{Languages/Lang|pl|{{{1|}}}|
}}{{Languages/Lang|pt|{{{1|}}}|
}}{{Languages/Lang|pt-br|{{{1|}}}|
}}{{Languages/Lang|ro|{{{1|}}}|
}}{{Languages/Lang|ru|{{{1|}}}|
}}{{Languages/Lang|si|{{{1|}}}|
}}{{Languages/Lang|sk|{{{1|}}}|
}}{{Languages/Lang|sl|{{{1|}}}|
}}{{Languages/Lang|so|{{{1|}}}|
}}{{Languages/Lang|sq|{{{1|}}}|
}}{{Languages/Lang|sr|{{{1|}}}|
}}{{Languages/Lang|sv|{{{1|}}}|
}}{{Languages/Lang|ta|{{{1|}}}|
}}{{Languages/Lang|th|{{{1|}}}|
}}{{Languages/Lang|tr|{{{1|}}}|
}}{{Languages/Lang|uk|{{{1|}}}|
}}{{Languages/Lang|vi|{{{1|}}}|
}}{{Languages/Lang|yi|{{{1|}}}|
}}{{Languages/Lang|yue|{{{1|}}}|
}}{{Languages/Lang|zh|{{{1|}}}|
}}{{Languages/Lang|zh-hans|{{{1|}}}|
}}{{Languages/Lang|zh-hant|{{{1|}}}|
}}{{Languages/Lang|zh-tw|{{{1|}}}}}
||[[Category:Languages pages without translations]]}}&lt;!--
--&gt;[[Category:Languages pages]]&lt;!--
--&gt;{{#ifeq:{{translation}}|/en||[[Category:Languages pages{{translation}}]]}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{ {{TNTN|documentation}} }}
[[Category:Exclude in print]]
&lt;/noinclude&gt;</text>
    <sha1>aa0a3f30852c3d71ab7babadb5e80e3de93f2495</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Languages/Lang</title>
  <ns>10</ns>
  <id>135</id>
  <revision>
    <id>320</id>
    <parentid>319</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="299" xml:space="preserve">{{#ifexist: {{#if:{{{2|}}}|{{{2}}}|{{NAMESPACE}}:{{BASEPAGENAME}}}}/{{{1|}}}
|&amp;nbsp;• &lt;bdi lang="{{{1|}}}"&gt;{{#if:{{{2|}}}
  |[[:{{{2|}}}/{{{1|}}}|{{#language:{{{1|}}}}}]]
  |[[:{{NAMESPACE}}:{{BASEPAGENAME}}/{{{1|}}}|{{#language:{{{1|}}}}}]]
  }}&lt;/bdi&gt;
}}&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>c21fa44889712c6aa27a79bb3191f2f6e29563f4</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Languages/Title</title>
  <ns>10</ns>
  <id>136</id>
  <revision>
    <id>322</id>
    <parentid>321</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3087" xml:space="preserve">{{LangSwitch|lang={{{1|}}}
|default=Language:
|Languages=Languages:
|MediaWiki=Languages:
|af=Taal:
|aln=Gjuha:
|am=ቋምቋ፦
|an=Idioma:
|ang=Sprǣc:
|ar=:اللغة
|arc=ܠܫܢܐ:
|arn=Dungun:
|arz=:اللغة
|as=ভাষা:
|ast=Llingua:
|avk=Ava:
|ay=Aru:
|az=Dil:
|bat-smg=Kalba:
|bcc=زبان:
|bcl=Tataramon:
|be=Мова:
|be-tarask=Мова:
|bg=Език:
|bn=ভাষা:
|br=Yezh :
|bs=Jezik:
|ca=Llengua :
|cdo=Ngṳ̄-ngiòng:
|ce=Мотт:
|ceb=Pinulongan:
|ch=Lengguahe:
|ckb-arab=زمان:
|co=Lingua :
|crh-cyrl=Тиль:
|crh-latn=Til:
|cs=Jazyk:
|cu=ѩꙁꙑ́къ :
|cv=Чĕлхе:
|cy=Iaith:
|da=Sprog:
|de=Sprache:
|diq=Zıwan:
|dsb=Rěc:
|ee=Gbe:
|el=Γλώσσα:
|en=Language:
|eo=Lingvo:
|es=Idioma:
|et=Keel:
|eu=Hizkuntza:
|ext=Palra:
|fa=زبان:
|fi=Kieli:
|fo=Mál:
|fr=Langue :
|frc=Langue :
|frp=Lengoua :
|fur=Lenghe :
|fy=Taal:
|ga=Teanga:
|gag=Dil:
|gan-hans=语言:
|gan-hant=語言:
|gl=Lingua:
|gn=Ñe'ẽ:
|got=Razda:
|grc=Γλῶσσα:
|gsw=Sproch:
|gu=ભાષા:
|gv=Çhengey:
|hak=Ngî-ngièn:
|haw=Kou 'ōlelo:
|he=שפה:
|hi=भाषा:
|hif-latn=Bhasa:
|hr=Jezik:
|hsb=Rěč:
|ht=Lang:
|hu=Nyelv:
|hy=Լեզու.
|ia=Lingua:
|id=Bahasa:
|ie=Lingue:
|ilo=Lengguahe:
|io=Linguo:
|is=Tungumál:
|it=Lingua:
|ja=言語:
|jv=Basa:
|ka=ენა:
|kaa=Til:
|kab=Tutlayt:
|kg=Ndinga:
|kiu=Zon:
|kk-arab=:ٴتىل
|kk-cyrl=Тіл:
|kk-latn=Til:
|km=ភាសា៖
|kn=ಭಾಷೆ:
|ko=언어:
|ksh=Sproch:
|ku-latn=Ziman:
|kv=Кыв:
|kw=Yeth:
|ky=Тил:
|la=Lingua:
|lb=Sprooch:
|lfn=Lingua:
|li=Taol:
|lij=Lengoa:
|loz=Zwa Siselect:
|lt=Kalba:
|lv=Valoda:
|lzh=語：
|mdf=Кяль:
|mg=fiteny:
|mhr=Йылме:
|min=Bahaso:
|mk=Јазик:
|ml=ഭാഷ:
|mn=Хэл:
|mr=भाषा:
|ms=Bahasa:
|mt=Lingwa:
|mwl=Lhéngua:
|my=ဘာသာ:
|myv=Кель:
|nah=Tlahtōlli:
|nap=Lengua:
|nds=Spraak:
|nds-nl=Taal:
|ne=भाषा:
|new=भाषा:
|nl=Taal:
|nn=Språk:
|no=Språk:
|nso=Polelo:
|oc=Lenga :
|os=Æвзаг:
|pa=ਭਾਸ਼ਾ:
|pam=Amanu:
|pdc=Schprooch:
|pdt=Sproak:
|pl=Język:
|pms=Lenga:
|pnb=بولی:
|pnt=Γλώσσαν:
|prg=Bilā:
|ps=ژبه:
|pt|pt-br=Língua:
|qu=Rimay:
|rm=Lingua:
|ro=Limba:
|roa-tara=Lénga:
|ru=Язык:
|sa=भाषा:
|sah=Омугун тыла:
|sc=Limba:
|scn=Lingua:
|sco=Leid:
|sdc=Linga:
|se=Giella:
|sei=Itom:
|sh=Jezik:
|shi=tutlayt:
|si=භාෂාව:
|sk=Jazyk:
|sl=Jezik:
|sli=Sproache:
|so=Luqada:
|sq=Gjuha:
|sr-ec=Језик:
|sr-el=Jezik:
|srn=Tongo:
|ss=Lúlwîmi:
|stq=Sproake:
|su=Basa:
|sv=Språk:
|sw=Lugha:
|szl=Godka:
|ta=மொழி:
|te=భాష:
|tet=Lian:
|tg-cyrl=Забон:
|th=ภาษา:
|ti=ቋንቋ:
|tk=Dil:
|tl=Wika:
|to=Lea:
|tr=Dil:
|tt-cyrl=Тел:
|tyv=Дыл:
|ug-arab=:تىل
|ug-latn=Til:
|uk=Мова:
|vec=Lengua:
|vep=Kel’:
|vi=Ngôn ngữ:
|vo=Pük:
|vro=Kiil:
|wa=Lingaedje:
|war=Yinaknan:
|wo=Làkk:
|wuu=语言:
|xal=Келн:
|xh=Ulwimi:
|xmf=ნინა:
|yi=שפראך:
|yo=Èdè:
|yue=語言:
|zea=Taele:
|zh=語言:
|zh-hans=语言:
|zh-hant=語言:
|zu=Ulimi:
}}&lt;noinclude&gt;{{Documentation}}&lt;/noinclude&gt;</text>
    <sha1>9a6086fadca92393091513e283c466a398fdea1d</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Nmbox</title>
  <ns>10</ns>
  <id>137</id>
  <revision>
    <id>324</id>
    <parentid>323</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="599" xml:space="preserve">&lt;table class="nmbox" style="border:1px solid #AAA; border-collapse:collapse; clear:both; font-size:85%; margin: 0.5em 0"&gt;
&lt;tr style="background:#EEF3E2"&gt;
{{#if:{{{image|}}}{{{header|}}}
| &lt;th class="mbox-image" style="white-space:nowrap; padding:4px 1em; border-{{dir|{{pagelang}}|left|right}}:1px solid #aaa"&gt;{{{image|}}} {{{header|}}}&lt;/th&gt;
| &lt;td class="mbox-empty-cell"&gt;&lt;/td&gt;   &lt;!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --&gt;
}}
&lt;td class="mbox-text" style="background:#F6F9ED"&gt;{{{text|}}}&lt;/td&gt;
&lt;/tr&gt;&lt;/table&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
    <sha1>3e5942f8af86a878f6abd3a6eeec367502baea89</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Pagelang</title>
  <ns>10</ns>
  <id>138</id>
  <revision>
    <id>326</id>
    <parentid>325</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="613" xml:space="preserve">{{#ifeq:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}|{{#titleparts:{{{1|{{PAGENAME}}}}}|1}}||{{#ifeq:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}|{{lc:{{PAGENAME:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}}}}}|{{#ifeq:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}|{{urlencode:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}}}|{{#ifeq:{{lc:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}}}|{{ucfirst:{{lc:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}}}}}||{{#switch:{{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}|doc|layout|sandbox|testcases|init|preload=|#default={{#titleparts:{{{1|{{PAGENAME}}}}}||-1}}}}}}}}}}}}&lt;noinclude&gt;{{Documentation}}&lt;/noinclude&gt;</text>
    <sha1>58a30c2368e3eec4f48178a05f99574a886ee439</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Translation</title>
  <ns>10</ns>
  <id>139</id>
  <revision>
    <id>328</id>
    <parentid>327</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="489" xml:space="preserve">{{#ifeq:
  {{lc:{{#titleparts:{{FULLPAGENAME}}|1|-1}}}}&lt;!-- broken test; we should restrict to accept only subpages that could match a lowercase language code; keep any uppercase letter meaning not a language code --&gt;
| {{lc:{{#language:{{#titleparts:{{FULLPAGENAME}}|1|-1}}}}}}&lt;!-- broken test; fails on some languages whose  autonym is identical to their lowercase code --&gt;
|
| /{{#titleparts:{{FULLPAGENAME}}|1|-1}}
}}&lt;noinclude&gt;
{{documentation}}

[[Category:Translation]]
&lt;/noinclude&gt;</text>
    <sha1>df4871b4aa9beb7ee2f6e276d9819d0a4dfc4541</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Uselang</title>
  <ns>10</ns>
  <id>140</id>
  <revision>
    <id>330</id>
    <parentid>329</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="138" xml:space="preserve">{{#if: {{{lang|}}} | {{{lang|}}} | {{#ifeq: {{int:Lang}} | &lt;Lang&gt; | default | {{int:Lang}} }} }}&lt;noinclude&gt;
{{Documentation}}
&lt;/noinclude&gt;</text>
    <sha1>297a29f24992bc20bf1a8d217933907f49e263e4</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Collapse top/doc</title>
  <ns>10</ns>
  <id>141</id>
  <revision>
    <id>332</id>
    <parentid>331</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="376" xml:space="preserve">&lt;noinclude&gt;{{Documentation subpage}}
{{timw|{{BASEPAGENAME}}}}
&lt;/noinclude&gt;
&lt;!-- PUT HERE THE DOCUMENTATION --&gt;
Use with {{tl|Collapse bottom}}, putting the content to be collapsed between the two templates.

This template has many parameters ''that should be documented here''.
For now, see the documentation for [[w:Template:Collapse top|the equivalent template on enwiki]].</text>
    <sha1>f6192f75f65394f03685259cce62518779d67256</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:TNTN</title>
  <ns>10</ns>
  <id>81</id>
  <revision>
    <id>334</id>
    <parentid>219</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="49" xml:space="preserve">#REDIRECT [[Template:Translatable template name]]</text>
    <sha1>51aba18c9e7edde0de5272258792895d16b983c2</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Translatable template name</title>
  <ns>10</ns>
  <id>82</id>
  <revision>
    <id>336</id>
    <parentid>220</parentid>
    <timestamp>2016-01-06T06:55:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="314" xml:space="preserve">&lt;includeonly&gt;{{#invoke:Template translation{{{sandbox|}}}|getTranslatedTemplate|uselang={{{uselang|}}}|tntns={{{tntns|{{{namespace|}}}}}}|template={{#if:{{{noshift|}}}|{{{template}}}|{{{1}}}}}|noshift={{{noshift|}}}&lt;!-- there are no other parameters here --&gt;}}&lt;/includeonly&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>cf01b803bccfc7ef72e324dc96840b2d093194a4</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>MediaWiki:Common.css</title>
  <ns>8</ns>
  <id>40</id>
  <revision>
    <id>337</id>
    <parentid>192</parentid>
    <timestamp>2016-01-06T08:40:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>css</model>
    <format>text/css</format>
    <text bytes="8661" xml:space="preserve">/* CSS placed here will be applied to all skins */

.smwbuiltin a,
.smwbuiltin a.new {
    color: #FF8000;
}

/* CSS placed here will be applied to all skins */

/* MediaWiki overrides */
/* body.page-Main_Page h1.firstHeading { display:none; } */
#footer-info { display: none; } /* Hide footer */
li#ca-talk { display: none; } /* Hide discussion tab */
#pt-login { display: none; } /* Hide login text */
#p-tb { display: none; } /* Hide toolbox */
/* #ca-history { display: none; } /* Hide "View history" */


/* Elements */
code { background: none; font: 10pt courier,serif; }
h2 { margin-top: 15px; }
h3 { color: #222; font-size: 11pt; margin: 10px 0 -5px; }
ol img { display: block; margin: 10px 10px 20px; }
ol li {  }
p  { margin-top: 10px; }
pre { background: #efefef; border: none; font: 10pt courier,serif; margin: 15px 0; padding: 10px; }
tt { font-size: 10pt; }

/* Controls */
.searchButton { background: #eee; border: 1px solid #ccc; color: #333; font: bold 8pt sans-serif; height: 20px; }

/* Boxes */
.fullbox { border: 1px solid #ccc; margin:5px; }
.title { background: #e8f2f8; border: none; border-bottom: 1px solid #ccc; color: #0e3793; font: bold 14pt sans-serif; margin: 0; padding: 5px; }
.subtitle { font: bold 10pt sans-serif; }
.example { background: #efefef; display: block; margin: 15px 0; padding: 10px; }

/* Formatting */
.clear { clear: both; }
.code { font: 10pt courier,serif; }
.hash { color: #090; }
.content { padding: 10px; }

/* Special elements */
div#kx-linkbar img { margin-right: 20px; }


.row {min-width:90% !important;}
.toctoggle {display:none}

table.wikitable &gt; tr &gt; th, 
table.wikitable &gt; tr &gt;td, 
table.wikitable &gt; * &gt; tr &gt;th, 
table.wikitable &gt; * &gt; tr &gt; td {
padding: 1px;
}
/*
div#viki_0{
width:100% !important;
}*/
.vikijs-detail-panel {
border:none !important;
background:white !important;
font-size:90%;
}
.vikijs-graph-container {
border:none !important;
}
.smwtable .row-even {
	background-color:#FFF;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
.smwtable .row-odd .stripe {
	background-color:#f0f7f8;
	text-align:left;
	padding-left:0;
	margin-left: 0;
	padding-right:0;
	margin-right: 0;
	list-style-position:inside;
}
h3#tagline {display:none; }
#footer-privacy {display:none}
#footer-disclaimer {display:none}
#footer-about {display:none}
#footer-lastmod {font-size:70%;}
#footer-viewcount {font-size:70%;}

p.title {
color:#009933;
font-size:100%;
}
h2 {
 font-size:125%;
}

h5 {
color: #666666;
}
.mw-search-formheader  {display:none; }
.thumbinner {
padding-left:5px;
padding-top:5px;
padding-bottom:5px;
}
.thumbcaption {
font-size:100%;
color:#009933;
background: white;
text-align: center;
}

h4 {
color:#009933;
}

form#sfForm.createbox, .formtable, table.formtable tr {
 background-color:#F0F8FF  !important;
}
form#sfForm.createbox, table.formtable tbody tr td table {
border: 1px solid #F0F8FF  !important;
}
option {
    font-weight:normal;
   font-size: x-small;
}
.createboxInput {
       background-color:#FFFFFF  !important;
}
.navbar-item {
	color: white !important;
	font-weight: bold;
	padding-top: 9px;
	padding-right: 10px;
}
.title {
	color:#009933;
        text-align: left;
        font-size:150%;
}

.top-bar,
.top-bar-section ul,
.top-bar-section ul li.active &gt; a,
.top-bar-section li a:not(.button),
.top-bar-section .has-form {
background:#061734;
font-size:90%;
color: #FFFFFF;
}

.top-bar-section &gt; ul &gt; .divider,
.top-bar-section &gt; ul &gt; [role="separator"] {
  border-color: #164eaf;
}

/* Darker color for the hover over items */
.top-bar-section ul li.hover &gt; a,
.top-bar-section ul li ul.dropdown li.hover &gt; a{
    background: #113e8c;
}

/* Slightly darker color for the dropdowns*/ 
.top-bar-section ul li ul.dropdown li &gt; a {
    background: #061734;
}
.spacer {
        height: 30px;
}
.np {
        height: 15px;
}
.hierarchyText {
        font-size:80%;
        font-weight:bold;
        height: 20px;
}
.hierarchyText table tbody tr  {
       background-color: #d5f99b;
       border: 1px solid #BFE08B;
       height: 20px;
}

.examplebread table tbody tr {
 background-color: #ADDFFF;
}

.citationtable {
	border: solid 1px #BBBBBB;
}

.citationtable td {
	padding-left: 5px;
	padding-right: 5px;
	max-width: 600px;
}
.citationtablelong td {
	padding-left: 5px;
	padding-right: 5px;
}

.itemtable td {
	vertical-align: top;
	min-width: 200px;
}

.ratingselected a {
	font-weight: bold;
	color: orange !important;
}

.nowrap {
	white-space: nowrap;
}
.filtered-filters { 
    float: left;
    width: 30%;
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    background: transparent;
}

.filtered-filters .filtered-value .filtered-value-option {
    display: block !important;
    width: 90% !important;
    padding: 0 !important;
}
 
.filtered-views { 
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    max-height: 800px;
}
 
.filtered-views .filtered-list { 
    width: 95% !important;
}
 
.filter_name {
    width: 150px;
    background:#96aab2;
    color:black;
    text-align:left;
    align:left;
    border:1px solid #ddd;
    padding: 3px;
}
 
.filter_value {
    width: 400px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.filter_icon {
    width: 50px;
    text-align:left;
    border: 1px solid #ddd;
    padding: 3px;
    background: white;
}
.top-bar.expanded .title-area {
   background:#164eaf;
}

/* CSS placed here will be applied to all skins */
#ca-protect { display: none !important; } 
#ca-delete { display: none !important; } 
.toc, #toc { display: none; }

/**
 * SECTION: SMW-Style Infoboxes
 *
 * Many "infoboxes" (not using Template:Infobox) have/had the CSS below
 * manually entered into each table. This was the case in Template:Award
 * and Template:Person. Now, instead, those "infoboxes" simply list class=
 * "smw-style-infobox-table" because this type of "infobox" is similar to 
 * what is used by SemanticMediaWiki and SemanticForms
 **/
.smw-style-infobox-table {
    width:            20em;
    font-size:        90%;
    border:           1px solid #aaaaaa;
    background-color: #f9f9f9;
    color:            black;
    margin-bottom:    0.5em;
    margin-left:      1em;
    padding:          0.2em;
    float:            right;
    clear:            right;
    text-align:       left;
    font-size:        92%;
}
.smw-style-infobox-table tr {
    vertical-align: top;
}
 
.smw-style-infobox-table-header {
    text-align:       center;
    background-color: #ccccff;
    font-size:        15px;
}
/**
 * END SECTION: SMW-Style Infoboxes
 **/

.agenda {
   text-align: left;
}
.agenda th {
   border: 1px solid #555555;
   background-color: #eeeeee;
   text-align: center;
   font-size: 120%;
}
.agenda td {
   border: 1px solid #555555;
   padding: 10px;
   vertical-align: top;
}

/* Float Left-Right-Center */
.chart-float-right {
	float:right;
	margin-left:10px;
	margin-bottom:10px;
	clear:both;
}
 
.chart-float-left {
	margin-left:0px;
	margin-right:10px;
	float:left;
	clear:both;
}
 
.chart-center {
	display: inline-block;
}

/**
 * SECTION: SMW-Style Infoboxes
 *
 * Many "infoboxes" (not using Template:Infobox) have/had the CSS below
 * manually entered into each table. This was the case in Template:Award
 * and Template:Person. Now, instead, those "infoboxes" simply list class=
 * "smw-style-infobox-table" because this type of "infobox" is similar to 
 * what is used by SemanticMediaWiki and SemanticForms
 **/
.smw-style-infobox-table {
    width:            20em;
    font-size:        90%;
    border:           1px solid #aaaaaa;
    background-color: #f9f9f9;
    color:            black;
    margin-bottom:    0.5em;
    margin-left:      1em;
    padding:          0.2em;
    float:            right;
    clear:            right;
    text-align:       left;
    font-size:        92%;
}
.smw-style-infobox-table tr {
    vertical-align: top;
}
 
.smw-style-infobox-table-header {
    text-align:       center;
    background-color: #ccccff;
    font-size:        15px;
}
/**
 * END SECTION: SMW-Style Infoboxes
 **/

.agenda {
   text-align: left;
}
.agenda th {
   border: 1px solid #555555;
   background-color: #eeeeee;
   text-align: center;
   font-size: 120%;
}
.agenda td {
   border: 1px solid #555555;
   padding: 10px;
   vertical-align: top;
}

/* Float Left-Right-Center */
.chart-float-right {
	float:right;
	margin-left:10px;
	margin-bottom:10px;
	clear:both;
}
 
.chart-float-left {
	margin-left:0px;
	margin-right:10px;
	float:left;
	clear:both;
}
 
.chart-center {
	display: inline-block;
}</text>
    <sha1>ed3f2eee26ce059a51e1ffcd736d5a2c9dc8aa14</sha1>
  </revision>
</page>
<page arvcontinue="20160106065535|244">
  <title>Template:Extension</title>
  <ns>10</ns>
  <id>80</id>
  <revision>
    <id>338</id>
    <parentid>218</parentid>
    <timestamp>2016-01-06T09:00:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Replaced content with "&lt;noinclude&gt; This is the "Extension" template. It should be called in the following format: &lt;pre&gt; {{Extension }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="222" xml:space="preserve">&lt;noinclude&gt;
This is the "Extension" template.
It should be called in the following format:
&lt;pre&gt;
{{Extension
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>b44a5371885e61528b3df5a60ab9812867fc081f</sha1>
  </revision>
  <revision>
    <id>339</id>
    <parentid>338</parentid>
    <timestamp>2016-01-06T09:00:22Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3880" xml:space="preserve">&lt;noinclude&gt;
This is the "Extension" template.
It should be called in the following format:
&lt;pre&gt;
{{Extension
|Name=
|Homepage=
|Description=
|Maintainer=
|First released month=
|First released year=
|Release status=
|Development status=
|Associated with=
|Area of usage=
|Shortcut=
|Repository=
}}
&lt;/pre&gt;
Edit the page to see the template text.

[[Category:Info templates]]

== Template preview ==
&lt;/noinclude&gt;&lt;onlyinclude&gt;
{| cellspacing="0" class="smworgtable" style="position: relative; float: right; clear: right; width: 280px;"
! colspan="2" style="padding-top: 2px; " | [[Has name::{{{Name|}}}]]
|-
| colspan="2" style="padding-top: 2px;" | '''[[Has description::{{{Description|}}}]]'''
|- &lt;!-- *** IMAGE SLIDESHOW *** --&gt;
{{#if:{{{collection|}}}|{{Tablesection|Label=Image collection|Color=#164eaf|Textcolor=#fff}}}}
|-
{{#if:{{{collection|}}}|{{Tablesection|Label={{#ask: [[has image collection::{{{collection|}}}]]|?has description|widths=220|heights=220|format=gallery|order=random|widget=slideshow|overlay=yes|class=demo-center|navigation=auto|autocaptions=no}}|Color=#fff|Textcolor=#AAA}}}}
|- &lt;!-- *** WORDCLOUD *** --&gt;
{{#if:{{{cloud|}}}|{{Tablesection|Label={{{cloud|}}}|Color=#fff|Textcolor=#AAA}}}}
|-
{{Tablesection|Label=Further Information|Color=#164eaf|Textcolor=#fff}}
|-
| style="width: 120px;" | Homepage: || [[Has homepage::{{{Homepage|}}}|follow this link]]
|-
| Maintainer(s): || {{#arraymap:{{{Maintainer|}}}|,|x|{{#set:Has maintainer=x}}{{Nowrap|[[x]]}}}}
|-
| First released: || [[Was first released month::{{{First released month|}}}]] [[Was first released year::{{{First released year|}}}]]
|-
| Release status: || [[Has release status::{{{Release status|}}}]]
|-
| Development status: || [[Has development status::{{{Development status|}}}]]
|-
| Area of usage: || [[Has area of usage::{{{Area of usage|}}}]]
|-
| Associated with:{{#info: SMW &amp;#61; [[Semantic MediaWiki]], SB &amp;#61; [[Semantic Bundle]], SMW+ &amp;#61; [[Semantic MediaWiki Plus]], MW &amp;#61; [[MediaWiki]]}}  || {{#arraymap:{{{Associated with|}}}|,|x|[[Is associated with::x]]}}
|- &lt;!-- *** SHORTCUT *** --&gt;
{{#ifeq:{{{Shortcut|}}}|||{{Tablerow|Label=Shortcut:{{#info: This is the shortcut to mark the beginning of the subject line when writing a support request to the mailing list or to the extension's author directly. See also this [[Help:Getting support|help page.]]}}|Value=[[Has shortcut::{{{Shortcut|}}}|{{uc: {{{Shortcut|}}} }}]] }}}}
|- &lt;!-- *** URL GIT/SVN *** --&gt;
{{#ifeq:{{{Repository|}}}|||{{Tablerow|Label=Repository:|Value={{{repository|{{{Repository|}}}}}} }}}}
|-
{{Tablesection|Label=Table of Contents|Color=#164eaf|Textcolor=#fff}}
|-
| colspan="2" style="padding-top: 2px; " |&lt;div id="smworgtable-toc" style="font-size: 90%;"&gt;__TOC__&lt;/div&gt;
|}&lt;includeonly&gt;{{#ifeq: {{{lang|}}} | zh-hans | [[Was first released::{{{First released year|}}}{{{First released month|}}}| ]] | [[Was first released::{{{First released month|}}} {{{First released year|}}}| ]] }}{{#ifeq: {{{Associated with|}}} | MW | [[Category:MW extensions]] | }}{{#ifeq: {{{Associated with|}}} | SMW | [[Category:SMW extensions]] | }}
{{#ifeq: {{{Associated with|}}} | SB | [[Category:Semantic Bundle extensions]] | }}{{#ifeq: {{{Associated with|}}} | SMW+ | [[Category:SMW+ extensions]] }}{{#ifeq: {{{Associated with|}}} | MW, SB | [[Category:MW extensions]] [[Category:Semantic Bundle extensions]] | }}{{#ifeq: {{{Associated with|}}} | MW, SMW | [[Category:MW extensions]] [[Category:SMW extensions]] | }}{{#ifeq: {{{Associated with|}}} | SMW, SB | [[Category:SMW extensions]] [[Category:Semantic Bundle extensions]] | }}{{#ifeq: {{{Associated with|}}} | SMW, SMW+ | [[Category:SMW extensions]] [[Category:SMW+ extensions]] | }}{{#ifeq: {{{Associated with|}}} | MW, SMW, SB | [[Category:MW extensions]] [[Category:SMW extensions]] [[Category:Semantic Bundle extensions]] | }}&lt;/includeonly&gt;&lt;/onlyinclude&gt;</text>
    <sha1>26d6dc8a818ae807bf58a56b8eb2dba3217aab63</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:Tablesection</title>
  <ns>10</ns>
  <id>142</id>
  <revision>
    <id>340</id>
    <timestamp>2016-01-06T09:01:01Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt;{| ! A  ! table section (helper template) |- &lt;/noinclude&gt;! colspan="2" style="text-align: center; color: {{{Textcolor|#000}}}; background: {{{Color|#eee}}}"| {{{Lab..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="206" xml:space="preserve">&lt;noinclude&gt;{|
! A 
! table section (helper template)
|-
&lt;/noinclude&gt;! colspan="2" style="text-align: center; color: {{{Textcolor|#000}}}; background: {{{Color|#eee}}}"| {{{Label}}}
&lt;noinclude&gt;|}&lt;/noinclude&gt;</text>
    <sha1>609bc87b5206387afec956de12258cc65cb1bb32</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:Datatype</title>
  <ns>10</ns>
  <id>143</id>
  <revision>
    <id>341</id>
    <timestamp>2016-01-06T09:02:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Datatype" template. It should be called in the following format: &lt;pre&gt; {{Datatype }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;inclu..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="220" xml:space="preserve">&lt;noinclude&gt;
This is the "Datatype" template.
It should be called in the following format:
&lt;pre&gt;
{{Datatype
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>8b1e953b9b36a9ab009491791782d609bbb066d1</sha1>
  </revision>
  <revision>
    <id>342</id>
    <parentid>341</parentid>
    <timestamp>2016-01-06T09:03:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1616" xml:space="preserve">&lt;noinclude&gt;
This is the '''Datatype''' template, used on [[:Category:Datatypes|'''Datatypes''' documentation pages]]. The template takes the following parameters:
* ''datatype name'': The actual name of the datatype.
* ''description'': a short text describing the datatype
* ''component'': The extension that provides this datatype, i.e. SMW, SM, etc.
* ''minimum version'': The minimum version of the extension you need for this datatype. Aka when it was added.

It is used like this:
&lt;pre&gt;{{Datatype
| datatype name=foobar
| description=Stores semantic data as foo bar.
| component=Semantic MediaWiki
| minimum version=1.0
| maximum version=1.8
}}&lt;/pre&gt;
[[Category:Info templates]]

== Template preview ==
&lt;/noinclude&gt;&lt;onlyinclude&gt;
{| cellspacing="0" class="smworgtable" style="position: relative; float: right; clear: right; width: 280px;"
! colspan="2" style="padding-top: 2px; " | [[Has datatype name::{{{datatype name|}}}]]
|-
| colspan="2" style="padding-top: 2px; " | '''[[Has description::{{{description|}}}]]'''
|-
{{Tablesection|Label=Further Information|Color=#164eaf|Textcolor=#fff}}
|-
| style="width: 120px;" | Provided by: || [[Has component::{{{component|not specified}}}]]
|-
|  Added in version: || [[Has minimum version::{{{minimum version|not specified}}}]]
|-
|  Removed in version: || [[Has maximum version::{{{maximum version|still in use}}}]]
|-
{{Tablesection|Label=Table of Contents|Color=#164eaf|Textcolor=#fff}}
|-
| colspan="2" style="padding-top: 2px; " |&lt;div id="smworgtable-toc" style="font-size: 90%;"&gt;__TOC__&lt;/div&gt;
|}&lt;includeonly&gt;[[Category:Datatypes]]&lt;/includeonly&gt;
&lt;/onlyinclude&gt;</text>
    <sha1>1e45be01f2670a2a422745cb7efc51f7e315b5e0</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Category:Datatypes</title>
  <ns>14</ns>
  <id>144</id>
  <revision>
    <id>343</id>
    <timestamp>2016-01-06T09:04:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This is the datatypes category."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="31" xml:space="preserve">This is the datatypes category.</text>
    <sha1>092cefcf6e689d5fd9d295ff72466e044e7d6e29</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:Class links</title>
  <ns>10</ns>
  <id>145</id>
  <revision>
    <id>344</id>
    <timestamp>2016-01-06T09:11:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Class links" template. It should be called in the following format: &lt;pre&gt; {{Class links }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="226" xml:space="preserve">&lt;noinclude&gt;
This is the "Class links" template.
It should be called in the following format:
&lt;pre&gt;
{{Class links
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>0504f5a5eec900ce74d85e88b8b6e77c32741674</sha1>
  </revision>
  <revision>
    <id>345</id>
    <parentid>344</parentid>
    <timestamp>2016-01-06T09:11:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="87" xml:space="preserve">[[Form:{{{1}}}|Form]], [[Template:{{{1}}}|Template]] and [[Category:{{{1}}}|Category]].</text>
    <sha1>4a310551c1da01cb47557c6d466232165dd7c95c</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Aligns with</title>
  <ns>102</ns>
  <id>146</id>
  <revision>
    <id>346</id>
    <timestamp>2016-01-06T09:15:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Page]].</text>
    <sha1>a77920a9d24db1d24320cdd74718a3bf351bd0c9</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Adversarial with</title>
  <ns>102</ns>
  <id>147</id>
  <revision>
    <id>347</id>
    <timestamp>2016-01-06T09:16:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Page]].</text>
    <sha1>a77920a9d24db1d24320cdd74718a3bf351bd0c9</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:Tool</title>
  <ns>10</ns>
  <id>148</id>
  <revision>
    <id>348</id>
    <timestamp>2016-01-06T09:23:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Tool" template. It should be called in the following format: &lt;pre&gt; {{Tool }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;includeonly&gt;{..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="212" xml:space="preserve">&lt;noinclude&gt;
This is the "Tool" template.
It should be called in the following format:
&lt;pre&gt;
{{Tool
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>326330c5ce54eafbdfe1f6c59bf37319ac2f47f2</sha1>
  </revision>
  <revision>
    <id>349</id>
    <parentid>348</parentid>
    <timestamp>2016-01-06T09:23:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2423" xml:space="preserve">{{Infobox
| bodystyle   = 
| bodyclass   = 

| title       = {{#if: {{{Ops Nom|}}} | {{{Ops Nom|}}} | Tool Info }}
| titlestyle  = 
| titleclass  = 

| headerstyle = 
| labelstyle  = 
| datastyle   = 

| image1    = {{#if: {{{image1|}}} | {{#if: {{#pos:{{{image1|}}}|.}} | {{#if:{{{image1|}}}|[[File:{{{image1|}}}|300px]]|}} | &lt;img src="{{IO Link | lores | {{{image1}}} }}" style="width:300px;" /&gt; &lt;br /&gt;[{{IO Link | hires | {{{image1}}} }} {{{image1}}}] }} | }}

| image2    = {{#if: {{{image2|}}} | {{#if: {{#pos:{{{image2|}}}|.}} | {{#if:{{{image2|}}}|[[File:{{{image2|}}}|300px]]|}} | &lt;img src="{{IO Link | lores | {{{image2}}} }}" style="width:300px;" /&gt; &lt;br /&gt;[{{IO Link | hires | {{{image2}}} }} {{{image2}}}] }} | }}

| header1  =
| label1   = [[Ops Nom]]
| data1    = {{#if: {{{Ops Nom|}}} | [[Ops Nom::{{{Ops Nom|}}}]] | }}
| header2  = 
| label2   = Alias
| data2    = {{#if: {{{Alias|}}} | [[Alias::{{{Alias|}}}]] | }}
| header3  = 
| label3   = Part Number
| data3    = {{#if: {{{Part_Number|}}} | [[Part_Number::{{{Part_Number|}}}]] | }}
| header4  = 
| label4   = Links
| data4    = {{#if: {{{Part_Number|}}} | [https://mod2.jsc.nasa.gov/ims/1Searchall.asp?keyword1={{{Part_Number}}}&amp;sortby=a&amp;searchIMS=Search IMS]&lt;br /&gt; | }}
{{#if: {{{Part_Number|}}} | [http://qfed-sma.jsc.nasa.gov/CDS/CDS/Certification/Search/Results2.aspx?&amp;Type=Part&amp;PartNumber={{{Part_Number}}} Certification]&lt;br /&gt; | }}
{{#if: {{{EDCC_Link|}}} | [{{{EDCC_Link}}} Drawing] (NDC Credentials) | }}
{{#if: {{{Part_Number|}}} | [https://mycmc-apps.jsc.nasa.gov/CMCImagery/ImageBrowser/imageviewer.html?pn={{{Part_Number}}} CMC Imagery]&lt;br /&gt; | }}
| header5  = 
| label5   = Mass (lbs.)
| data5    = {{#if: {{{Mass|}}} | [[Mass::{{{Mass|}}}]] | }}
| header6  = 
| label6   = Length (in.)
| data6    = {{#if: {{{Length|}}} | [[Length::{{{Length|}}}]] | }}
| header7  = 
| label7   = Width (in.)
| data7    = {{#if: {{{Width|}}} | [[Width::{{{Width|}}}]] | }}
| header8  = 
| label8   = Height (in.)
| data8    = {{#if: {{{Height|}}} | [[Height::{{{Height|}}}]] | }}
| header9  = 
| label9   = Parent
| data9    = {{#if: {{{Parent|}}} | [[Parent::{{{Parent|}}}]] | }}
| header10 = 
| label10  = Mounted RETs
| data10   = {{#if: {{{Mounted RETs|}}} | [[Has Quantity Mounted RETs::{{{Mounted RETs|}}}]] | }}
|belowstyle = 
|below = 
}}[[Category:Tool]]{{#if: {{{image1|}}} | {{#set: Primary image = {{{image1|}}} }} | }}
&lt;noinclude&gt;
&lt;/noinclude&gt;</text>
    <sha1>245b772be3c4e792eca8c675e45e236fda1a29b8</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:Infobox</title>
  <ns>10</ns>
  <id>149</id>
  <revision>
    <id>350</id>
    <timestamp>2016-01-06T09:26:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{#ifeq:{{{child|}}}|yes||&lt;table class="infobox {{{bodyclass|}}}" cellspacing="5" style="width:22em; {{{bodystyle|}}}"&gt;&lt;!--  Caption --&gt;{{#if:{{{title|}}}|&lt;caption class="{{{t..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="21895" xml:space="preserve">{{#ifeq:{{{child|}}}|yes||&lt;table class="infobox {{{bodyclass|}}}" cellspacing="5" style="width:22em; {{{bodystyle|}}}"&gt;&lt;!--
 Caption
--&gt;{{#if:{{{title|}}}|&lt;caption class="{{{titleclass|}}}" style="{{{titlestyle|}}}"&gt;{{{title}}}&lt;/caption&gt;}}&lt;!--
 Header
--&gt;{{#if:{{{above|}}}|&lt;tr&gt;&lt;th colspan=2 class="{{{aboveclass|}}}" style="text-align:center; font-size:125%; font-weight:bold; {{{abovestyle|}}}"&gt;{{{above}}}&lt;/th&gt;&lt;/tr&gt;}}
}}{{#ifeq:{{{child|}}}|yes|{{#if:{{{title|}}}|'''{{{title}}}'''}}}}&lt;!--
 Subheader1
--&gt;{{#if:{{{subheader|{{{subheader1|}}}}}}|{{Infobox/row
 |data={{{subheader|{{{subheader1|}}}}}}
 |datastyle={{{subheaderstyle|{{{subheaderstyle1|}}}}}}
 |class={{{subheaderclass|}}}
 |rowclass={{{subheaderrowclass|{{{subheaderrowclass1|}}}}}}
}} }}&lt;!--
 Subheader2
--&gt;{{#if:{{{subheader2|}}}|{{Infobox/row
 |data={{{subheader2}}}
 |datastyle={{{subheaderstyle|{{{subheaderstyle2|}}}}}}
 |class={{{subheaderclass|}}}
 |rowclass={{{subheaderrowclass2|}}}
}} }}&lt;!--
 Image1
--&gt;{{#if:{{{image|{{{image1|}}}}}}|{{Infobox/row
 |data={{{image|{{{image1}}} }}}{{#if:{{{caption|{{{caption1|}}}}}}|&lt;br /&gt;&lt;span style="{{{captionstyle|}}}"&gt;{{{caption|{{{caption1}}}}}}&lt;/span&gt;}}
 |datastyle={{{imagestyle|}}}
 |class={{{imageclass|}}}
 |rowclass={{{imagerowclass1|}}}
}} }}&lt;!--
 Image2
--&gt;{{#if:{{{image2|}}}|{{Infobox/row
 |data={{{image2}}}{{#if:{{{caption2|}}}|&lt;br /&gt;&lt;span style="{{{captionstyle|}}}"&gt;{{{caption2}}}&lt;/span&gt;}}
 |datastyle={{{imagestyle|}}}
 |class={{{imageclass|}}}
 |rowclass={{{imagerowclass2|}}}
}} }}&lt;!--
--&gt;{{Infobox/row
 |header={{{header1|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label1|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data1|}}}     |datastyle={{{datastyle|}}}
 |class={{{class1|}}}   |rowclass={{{rowclass1|}}}
}}{{Infobox/row
 |header={{{header2|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label2|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data2|}}}     |datastyle={{{datastyle|}}}
 |class={{{class2|}}}   |rowclass={{{rowclass2|}}}
}}{{Infobox/row
 |header={{{header3|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label3|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data3|}}}     |datastyle={{{datastyle|}}}
 |class={{{class3|}}}   |rowclass={{{rowclass3|}}}
}}{{Infobox/row
 |header={{{header4|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label4|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data4|}}}     |datastyle={{{datastyle|}}}
 |class={{{class4|}}}   |rowclass={{{rowclass4|}}}
}}{{Infobox/row
 |header={{{header5|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label5|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data5|}}}     |datastyle={{{datastyle|}}}
 |class={{{class5|}}}   |rowclass={{{rowclass5|}}}
}}{{Infobox/row
 |header={{{header6|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label6|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data6|}}}     |datastyle={{{datastyle|}}}
 |class={{{class6|}}}   |rowclass={{{rowclass6|}}}
}}{{Infobox/row
 |header={{{header7|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label7|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data7|}}}     |datastyle={{{datastyle|}}}
 |class={{{class7|}}}   |rowclass={{{rowclass7|}}}
}}{{Infobox/row
 |header={{{header8|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label8|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data8|}}}     |datastyle={{{datastyle|}}}
 |class={{{class8|}}}   |rowclass={{{rowclass8|}}}
}}{{Infobox/row
 |header={{{header9|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label9|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data9|}}}     |datastyle={{{datastyle|}}}
 |class={{{class9|}}}   |rowclass={{{rowclass9|}}}
}}{{Infobox/row
 |header={{{header10|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label10|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data10|}}}     |datastyle={{{datastyle|}}}
 |class={{{class10|}}}   |rowclass={{{rowclass10|}}}
}}{{Infobox/row
 |header={{{header11|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label11|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data11|}}}     |datastyle={{{datastyle|}}}
 |class={{{class11|}}}   |rowclass={{{rowclass11|}}}
}}{{Infobox/row
 |header={{{header12|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label12|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data12|}}}     |datastyle={{{datastyle|}}}
 |class={{{class12|}}}   |rowclass={{{rowclass12|}}}
}}{{Infobox/row
 |header={{{header13|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label13|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data13|}}}     |datastyle={{{datastyle|}}}
 |class={{{class13|}}}   |rowclass={{{rowclass13|}}}
}}{{Infobox/row
 |header={{{header14|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label14|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data14|}}}     |datastyle={{{datastyle|}}}
 |class={{{class14|}}}   |rowclass={{{rowclass14|}}}
}}{{Infobox/row
 |header={{{header15|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label15|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data15|}}}     |datastyle={{{datastyle|}}}
 |class={{{class15|}}}   |rowclass={{{rowclass15|}}}
}}{{Infobox/row
 |header={{{header16|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label16|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data16|}}}     |datastyle={{{datastyle|}}}
 |class={{{class16|}}}   |rowclass={{{rowclass16|}}}
}}{{Infobox/row
 |header={{{header17|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label17|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data17|}}}     |datastyle={{{datastyle|}}}
 |class={{{class17|}}}   |rowclass={{{rowclass17|}}}
}}{{Infobox/row
 |header={{{header18|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label18|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data18|}}}     |datastyle={{{datastyle|}}}
 |class={{{class18|}}}   |rowclass={{{rowclass18|}}}
}}{{Infobox/row
 |header={{{header19|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label19|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data19|}}}     |datastyle={{{datastyle|}}}
 |class={{{class19|}}}   |rowclass={{{rowclass19|}}}
}}{{Infobox/row
 |header={{{header20|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label20|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data20|}}}     |datastyle={{{datastyle|}}}
 |class={{{class20|}}}   |rowclass={{{rowclass20|}}}
}}{{Infobox/row
 |header={{{header21|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label21|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data21|}}}     |datastyle={{{datastyle|}}}
 |class={{{class21|}}}   |rowclass={{{rowclass21|}}}
}}{{Infobox/row
 |header={{{header22|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label22|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data22|}}}     |datastyle={{{datastyle|}}}
 |class={{{class22|}}}   |rowclass={{{rowclass22|}}}
}}{{Infobox/row
 |header={{{header23|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label23|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data23|}}}     |datastyle={{{datastyle|}}}
 |class={{{class23|}}}   |rowclass={{{rowclass23|}}}
}}{{Infobox/row
 |header={{{header24|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label24|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data24|}}}     |datastyle={{{datastyle|}}}
 |class={{{class24|}}}   |rowclass={{{rowclass24|}}}
}}{{Infobox/row
 |header={{{header25|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label25|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data25|}}}     |datastyle={{{datastyle|}}}
 |class={{{class25|}}}   |rowclass={{{rowclass25|}}}
}}{{Infobox/row
 |header={{{header26|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label26|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data26|}}}     |datastyle={{{datastyle|}}}
 |class={{{class26|}}}   |rowclass={{{rowclass26|}}}
}}{{Infobox/row
 |header={{{header27|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label27|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data27|}}}     |datastyle={{{datastyle|}}}
 |class={{{class27|}}}   |rowclass={{{rowclass27|}}}
}}{{Infobox/row
 |header={{{header28|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label28|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data28|}}}     |datastyle={{{datastyle|}}}
 |class={{{class28|}}}   |rowclass={{{rowclass28|}}}
}}{{Infobox/row
 |header={{{header29|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label29|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data29|}}}     |datastyle={{{datastyle|}}}
 |class={{{class29|}}}   |rowclass={{{rowclass29|}}}
}}{{Infobox/row
 |header={{{header30|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label30|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data30|}}}     |datastyle={{{datastyle|}}}
 |class={{{class30|}}}   |rowclass={{{rowclass30|}}}
}}{{Infobox/row
 |header={{{header31|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label31|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data31|}}}     |datastyle={{{datastyle|}}}
 |class={{{class31|}}}   |rowclass={{{rowclass31|}}}
}}{{Infobox/row
 |header={{{header32|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label32|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data32|}}}     |datastyle={{{datastyle|}}}
 |class={{{class32|}}}   |rowclass={{{rowclass32|}}}
}}{{Infobox/row
 |header={{{header33|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label33|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data33|}}}     |datastyle={{{datastyle|}}}
 |class={{{class33|}}}   |rowclass={{{rowclass33|}}}
}}{{Infobox/row
 |header={{{header34|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label34|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data34|}}}     |datastyle={{{datastyle|}}}
 |class={{{class34|}}}   |rowclass={{{rowclass34|}}}
}}{{Infobox/row
 |header={{{header35|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label35|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data35|}}}     |datastyle={{{datastyle|}}}
 |class={{{class35|}}}   |rowclass={{{rowclass35|}}}
}}{{Infobox/row
 |header={{{header36|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label36|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data36|}}}     |datastyle={{{datastyle|}}}
 |class={{{class36|}}}   |rowclass={{{rowclass36|}}}
}}{{Infobox/row
 |header={{{header37|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label37|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data37|}}}     |datastyle={{{datastyle|}}}
 |class={{{class37|}}}   |rowclass={{{rowclass37|}}}
}}{{Infobox/row
 |header={{{header38|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label38|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data38|}}}     |datastyle={{{datastyle|}}}
 |class={{{class38|}}}   |rowclass={{{rowclass38|}}}
}}{{Infobox/row
 |header={{{header39|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label39|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data39|}}}     |datastyle={{{datastyle|}}}
 |class={{{class39|}}}   |rowclass={{{rowclass39|}}}
}}{{Infobox/row
 |header={{{header40|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label40|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data40|}}}     |datastyle={{{datastyle|}}}
 |class={{{class40|}}}   |rowclass={{{rowclass40|}}}
}}{{Infobox/row
 |header={{{header41|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label41|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data41|}}}     |datastyle={{{datastyle|}}}
 |class={{{class41|}}}   |rowclass={{{rowclass41|}}}
}}{{Infobox/row
 |header={{{header42|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label42|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data42|}}}     |datastyle={{{datastyle|}}}
 |class={{{class42|}}}   |rowclass={{{rowclass42|}}}
}}{{Infobox/row
 |header={{{header43|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label43|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data43|}}}     |datastyle={{{datastyle|}}}
 |class={{{class43|}}}   |rowclass={{{rowclass43|}}}
}}{{Infobox/row
 |header={{{header44|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label44|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data44|}}}     |datastyle={{{datastyle|}}}
 |class={{{class44|}}}   |rowclass={{{rowclass44|}}}
}}{{Infobox/row
 |header={{{header45|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label45|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data45|}}}     |datastyle={{{datastyle|}}}
 |class={{{class45|}}}   |rowclass={{{rowclass45|}}}
}}{{Infobox/row
 |header={{{header46|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label46|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data46|}}}     |datastyle={{{datastyle|}}}
 |class={{{class46|}}}   |rowclass={{{rowclass46|}}}
}}{{Infobox/row
 |header={{{header47|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label47|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data47|}}}     |datastyle={{{datastyle|}}}
 |class={{{class47|}}}   |rowclass={{{rowclass47|}}}
}}{{Infobox/row
 |header={{{header48|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label48|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data48|}}}     |datastyle={{{datastyle|}}}
 |class={{{class48|}}}   |rowclass={{{rowclass48|}}}
}}{{Infobox/row
 |header={{{header49|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label49|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data49|}}}     |datastyle={{{datastyle|}}}
 |class={{{class49|}}}   |rowclass={{{rowclass49|}}}
}}{{Infobox/row
 |header={{{header50|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label50|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data50|}}}     |datastyle={{{datastyle|}}}
 |class={{{class50|}}}   |rowclass={{{rowclass50|}}}
}}{{Infobox/row
 |header={{{header51|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label51|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data51|}}}     |datastyle={{{datastyle|}}}
 |class={{{class51|}}}   |rowclass={{{rowclass51|}}}
}}{{Infobox/row
 |header={{{header52|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label52|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data52|}}}     |datastyle={{{datastyle|}}}
 |class={{{class52|}}}   |rowclass={{{rowclass52|}}}
}}{{Infobox/row
 |header={{{header53|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label53|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data53|}}}     |datastyle={{{datastyle|}}}
 |class={{{class53|}}}   |rowclass={{{rowclass53|}}}
}}{{Infobox/row
 |header={{{header54|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label54|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data54|}}}     |datastyle={{{datastyle|}}}
 |class={{{class54|}}}   |rowclass={{{rowclass54|}}}
}}{{Infobox/row
 |header={{{header55|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label55|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data55|}}}     |datastyle={{{datastyle|}}}
 |class={{{class55|}}}   |rowclass={{{rowclass55|}}}
}}{{Infobox/row
 |header={{{header56|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label56|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data56|}}}     |datastyle={{{datastyle|}}}
 |class={{{class56|}}}   |rowclass={{{rowclass56|}}}
}}{{Infobox/row
 |header={{{header57|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label57|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data57|}}}     |datastyle={{{datastyle|}}}
 |class={{{class57|}}}   |rowclass={{{rowclass57|}}}
}}{{Infobox/row
 |header={{{header58|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label58|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data58|}}}     |datastyle={{{datastyle|}}}
 |class={{{class58|}}}   |rowclass={{{rowclass58|}}}
}}{{Infobox/row
 |header={{{header59|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label59|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data59|}}}     |datastyle={{{datastyle|}}}
 |class={{{class59|}}}   |rowclass={{{rowclass59|}}}
}}{{Infobox/row
 |header={{{header60|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label60|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data60|}}}     |datastyle={{{datastyle|}}}
 |class={{{class60|}}}   |rowclass={{{rowclass60|}}}
}}{{Infobox/row
 |header={{{header61|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label61|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data61|}}}     |datastyle={{{datastyle|}}}
 |class={{{class61|}}}   |rowclass={{{rowclass61|}}}
}}{{Infobox/row
 |header={{{header62|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label62|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data62|}}}     |datastyle={{{datastyle|}}}
 |class={{{class62|}}}   |rowclass={{{rowclass62|}}}
}}{{Infobox/row
 |header={{{header63|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label63|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data63|}}}     |datastyle={{{datastyle|}}}
 |class={{{class63|}}}   |rowclass={{{rowclass63|}}}
}}{{Infobox/row
 |header={{{header64|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label64|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data64|}}}     |datastyle={{{datastyle|}}}
 |class={{{class64|}}}   |rowclass={{{rowclass64|}}}
}}{{Infobox/row
 |header={{{header65|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label65|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data65|}}}     |datastyle={{{datastyle|}}}
 |class={{{class65|}}}   |rowclass={{{rowclass65|}}}
}}{{Infobox/row
 |header={{{header66|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label66|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data66|}}}     |datastyle={{{datastyle|}}}
 |class={{{class66|}}}   |rowclass={{{rowclass66|}}}
}}{{Infobox/row
 |header={{{header67|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label67|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data67|}}}     |datastyle={{{datastyle|}}}
 |class={{{class67|}}}   |rowclass={{{rowclass67|}}}
}}{{Infobox/row
 |header={{{header68|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label68|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data68|}}}     |datastyle={{{datastyle|}}}
 |class={{{class68|}}}   |rowclass={{{rowclass68|}}}
}}{{Infobox/row
 |header={{{header69|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label69|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data69|}}}     |datastyle={{{datastyle|}}}
 |class={{{class69|}}}   |rowclass={{{rowclass69|}}}
}}{{Infobox/row
 |header={{{header70|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label70|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data70|}}}     |datastyle={{{datastyle|}}}
 |class={{{class70|}}}   |rowclass={{{rowclass70|}}}
}}{{Infobox/row
 |header={{{header71|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label71|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data71|}}}     |datastyle={{{datastyle|}}}
 |class={{{class71|}}}   |rowclass={{{rowclass71|}}}
}}{{Infobox/row
 |header={{{header72|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label72|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data72|}}}     |datastyle={{{datastyle|}}}
 |class={{{class72|}}}   |rowclass={{{rowclass72|}}}
}}{{Infobox/row
 |header={{{header73|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label73|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data73|}}}     |datastyle={{{datastyle|}}}
 |class={{{class73|}}}   |rowclass={{{rowclass73|}}}
}}{{Infobox/row
 |header={{{header74|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label74|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data74|}}}     |datastyle={{{datastyle|}}}
 |class={{{class74|}}}   |rowclass={{{rowclass74|}}}
}}{{Infobox/row
 |header={{{header75|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label75|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data75|}}}     |datastyle={{{datastyle|}}}
 |class={{{class75|}}}   |rowclass={{{rowclass75|}}}
}}{{Infobox/row
 |header={{{header76|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label76|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data76|}}}     |datastyle={{{datastyle|}}}
 |class={{{class76|}}}   |rowclass={{{rowclass76|}}}
}}{{Infobox/row
 |header={{{header77|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label77|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data77|}}}     |datastyle={{{datastyle|}}}
 |class={{{class77|}}}   |rowclass={{{rowclass77|}}}
}}{{Infobox/row
 |header={{{header78|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label78|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data78|}}}     |datastyle={{{datastyle|}}}
 |class={{{class78|}}}   |rowclass={{{rowclass78|}}}
}}{{Infobox/row
 |header={{{header79|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label79|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data79|}}}     |datastyle={{{datastyle|}}}
 |class={{{class79|}}}   |rowclass={{{rowclass79|}}}
}}{{Infobox/row
 |header={{{header80|}}} |headerstyle={{{headerstyle|}}}
 |label={{{label80|}}}   |labelstyle={{{labelstyle|}}}
 |data={{{data80|}}}     |datastyle={{{datastyle|}}}
 |class={{{class80|}}}   |rowclass={{{rowclass80|}}}
}}&lt;!-- Below
--&gt;{{#if:{{{below|}}}|&lt;tr&gt;&lt;td colspan=2 class="{{{belowclass|}}}" style="text-align:center; {{{belowstyle|}}}"&gt;{{{below}}}&lt;/td&gt;&lt;/tr&gt;}}&lt;!--
 Navbar
--&gt;{{#if:{{{name|}}}|&lt;tr&gt;&lt;td colspan=2 style="text-align:right"&gt;{{navbar|{{{name}}}|mini=1}}&lt;/td&gt;&lt;/tr&gt;}}
{{#ifeq:{{{child|}}}|yes||&lt;/table&gt;}}{{#switch:{{lc:{{{italic title|¬}}}}}
 |¬|no       = &lt;!-- no italic title --&gt;
 ||force|yes = {{italic title|force={{#ifeq:{{lc:{{{italic title|}}}}}|force|true}}}}
}}&lt;includeonly&gt;{{#ifeq:{{{decat|}}}|yes||{{#if:{{{data1|}}}{{{data2|}}}{{{data3|}}}{{{data4|}}}{{{data5|}}}{{{data6|}}}{{{data7|}}}{{{data8|}}}{{{data9|}}}{{{data10|}}}{{{data11|}}}{{{data12|}}}{{{data13|}}}{{{data14|}}}{{{data15|}}}{{{data16|}}}{{{data17|}}}{{{data18|}}}{{{data19|}}}{{{data20|}}}{{{data21|}}}{{{data22|}}}{{{data23|}}}{{{data24|}}}{{{data25|}}}{{{data26|}}}{{{data27|}}}{{{data28|}}}{{{data29|}}}{{{data30|}}}{{{data31|}}}{{{data32|}}}{{{data33|}}}{{{data34|}}}{{{data35|}}}{{{data36|}}}{{{data37|}}}{{{data38|}}}{{{data39|}}}{{{data40|}}}{{{data41|}}}{{{data42|}}}{{{data43|}}}{{{data44|}}}{{{data45|}}}{{{data46|}}}{{{data47|}}}{{{data48|}}}{{{data49|}}}{{{data50|}}}{{{data51|}}}{{{data52|}}}{{{data53|}}}{{{data54|}}}{{{data55|}}}{{{data56|}}}{{{data57|}}}{{{data58|}}}{{{data59|}}}{{{data60|}}}{{{data61|}}}{{{data62|}}}{{{data63|}}}{{{data64|}}}{{{data65|}}}{{{data66|}}}{{{data67|}}}{{{data68|}}}{{{data69|}}}{{{data70|}}}{{{data71|}}}{{{data72|}}}{{{data73|}}}{{{data74|}}}{{{data75|}}}{{{data76|}}}{{{data77|}}}{{{data78|}}}{{{data79|}}}{{{data80|}}}||{{namespace detect|main=[[category:articles which use infobox templates with no data rows]]}}}}}}&lt;/includeonly&gt;&lt;noinclude&gt;{{documentation}}&lt;/noinclude&gt;</text>
    <sha1>5713b1e101127a7efaaf2c9bfac459d2ec817ac2</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:Infobox/row</title>
  <ns>10</ns>
  <id>150</id>
  <revision>
    <id>351</id>
    <timestamp>2016-01-06T09:30:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{#if:{{{header|}}}  |&lt;tr&gt;&lt;th colspan="2" class="{{{class|}}}" style="text-align:center; {{{headerstyle|}}}"&gt;{{{header}}}&lt;/th&gt;&lt;/tr&gt;  |{{#if:{{{data|}}}   |&lt;tr class="{{{rowcla..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="455" xml:space="preserve">{{#if:{{{header|}}}
 |&lt;tr&gt;&lt;th colspan="2" class="{{{class|}}}" style="text-align:center; {{{headerstyle|}}}"&gt;{{{header}}}&lt;/th&gt;&lt;/tr&gt;
 |{{#if:{{{data|}}}
  |&lt;tr class="{{{rowclass|}}}"&gt;{{#if:{{{label|}}}
   |&lt;th scope="row" style="text-align:left; {{{labelstyle|}}}"&gt;{{{label}}}&lt;/th&gt;
    &lt;td class="{{{class|}}}" style="{{{datastyle|}}}"&gt;
   |&lt;td colspan="2" class="{{{class|}}}" style="text-align:center; {{{datastyle|}}}"&gt;
  }}
{{{data}}}&lt;/td&gt;&lt;/tr&gt;
 }}
}}</text>
    <sha1>49a1f9f5c244da1b34e5bf561520bb7ad7fe0785</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Slides</title>
  <ns>0</ns>
  <id>151</id>
  <revision>
    <id>352</id>
    <timestamp>2016-01-06T10:36:31Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{#github:slides}}"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">{{#github:slides}}</text>
    <sha1>be57e93b05967be81c92b03d33b5f3d7811228da</sha1>
  </revision>
  <revision>
    <id>353</id>
    <parentid>352</parentid>
    <timestamp>2016-01-06T10:40:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="71" xml:space="preserve">{{#github:https://enterprisemediawiki.github.io/slides/MeetingMinutes}}</text>
    <sha1>c1cb9f00711db86e36ff375f9c1288e71b829856</sha1>
  </revision>
  <revision>
    <id>354</id>
    <parentid>353</parentid>
    <timestamp>2016-01-06T10:41:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="66" xml:space="preserve">{{#github:enterprisemediawiki.github.io/slides/MeetingMinutes/#/}}</text>
    <sha1>b03f0c5ee9965f08ab613ba5ba11475252569def</sha1>
  </revision>
  <revision>
    <id>355</id>
    <parentid>354</parentid>
    <timestamp>2016-01-06T10:43:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="54" xml:space="preserve">enterprisemediawiki.github.io/slides/MeetingMinutes/#/</text>
    <sha1>7be7f34b9d6ca14824a26f4198e93224bcc24a34</sha1>
  </revision>
  <revision>
    <id>356</id>
    <parentid>355</parentid>
    <timestamp>2016-01-06T10:44:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="55" xml:space="preserve">{{enterprisemediawiki.github.io/slides/MeetingMinutes}}</text>
    <sha1>993e2138851053b80adf8cbbe6f8e5d0329a0ac5</sha1>
  </revision>
  <revision>
    <id>357</id>
    <parentid>356</parentid>
    <timestamp>2016-01-06T10:44:41Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="62" xml:space="preserve">{{Github:enterprisemediawiki.github.io/slides/MeetingMinutes}}</text>
    <sha1>325cc277ef01e042089ce7b1996a0d7f4bf11d3b</sha1>
  </revision>
  <revision>
    <id>358</id>
    <parentid>357</parentid>
    <timestamp>2016-01-06T10:48:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="142" xml:space="preserve">{{Github:enterprisemediawiki.github.io/slides/MeetingMinutes}}

[[File:Http://enterprisemediawiki.github.io/slides/MeetingMinutes/|thumbnail]]</text>
    <sha1>1506d57bb9ed52663b715ac27648216e16897b37</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Display precision of</title>
  <ns>102</ns>
  <id>152</id>
  <revision>
    <id>359</id>
    <timestamp>2016-01-10T17:16:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Number]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="48" xml:space="preserve">This is a property of type [[Has type::Number]].</text>
    <sha1>9d3dff79653fddb88e6c584827d2b60c3056f646</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Has label</title>
  <ns>102</ns>
  <id>153</id>
  <revision>
    <id>360</id>
    <timestamp>2016-01-10T17:19:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
  <revision>
    <id>361</id>
    <parentid>360</parentid>
    <timestamp>2016-01-10T17:19:39Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="48" xml:space="preserve">This is a property of type [[Has type::String]].</text>
    <sha1>28995a61238b5697df1bb46875d44755b356227c</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Height</title>
  <ns>102</ns>
  <id>154</id>
  <revision>
    <id>362</id>
    <timestamp>2016-01-10T17:20:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Number]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="48" xml:space="preserve">This is a property of type [[Has type::Number]].</text>
    <sha1>9d3dff79653fddb88e6c584827d2b60c3056f646</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Namespace</title>
  <ns>102</ns>
  <id>155</id>
  <revision>
    <id>363</id>
    <timestamp>2016-01-10T17:23:22Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Subpage</title>
  <ns>102</ns>
  <id>156</id>
  <revision>
    <id>364</id>
    <timestamp>2016-01-10T17:26:40Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Page]].</text>
    <sha1>a77920a9d24db1d24320cdd74718a3bf351bd0c9</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Glossary-Definition</title>
  <ns>102</ns>
  <id>157</id>
  <revision>
    <id>365</id>
    <timestamp>2016-01-10T17:31:28Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Glossary-Term</title>
  <ns>102</ns>
  <id>158</id>
  <revision>
    <id>366</id>
    <timestamp>2016-01-10T17:32:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Category:Page</title>
  <ns>14</ns>
  <id>159</id>
  <revision>
    <id>367</id>
    <timestamp>2016-01-10T19:12:33Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This is the Page category.  [[Category:Hidden categories]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="58" xml:space="preserve">This is the Page category.

[[Category:Hidden categories]]</text>
    <sha1>4165b31771b13a3c7393d45124a8a4dc7151c678</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:URL</title>
  <ns>102</ns>
  <id>160</id>
  <revision>
    <id>368</id>
    <timestamp>2016-01-10T19:37:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::URL]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="45" xml:space="preserve">This is a property of type [[Has type::URL]].</text>
    <sha1>d2baf5c435e78f89e6dfbf0a19dfa3861a4cdf72</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Has area</title>
  <ns>102</ns>
  <id>161</id>
  <revision>
    <id>369</id>
    <timestamp>2016-01-10T19:39:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Quantity]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="50" xml:space="preserve">This is a property of type [[Has type::Quantity]].</text>
    <sha1>8090dc44d50899d1e940758dcee82aacc1940ef3</sha1>
  </revision>
  <revision>
    <id>370</id>
    <parentid>369</parentid>
    <timestamp>2016-01-10T19:40:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="351" xml:space="preserve">[[Has type::Quantity]] [[Has description::Used for property values that describe quantities, in particular physical quantities such as time or distance.]] [[Category:Lorem ipsum]]

* [[Corresponds to::1 km²]]
* [[Corresponds to::0.38610 sq mi]]   
* [[Corresponds to::1000 m²]]
* [[Corresponds to::247.1054 acre]]
* [[Corresponds to::988.4215 rood]]</text>
    <sha1>3149176f834dceac9afcd882010a6216a2cbcd69</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Has description</title>
  <ns>102</ns>
  <id>162</id>
  <revision>
    <id>371</id>
    <timestamp>2016-01-10T19:42:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
  <revision>
    <id>372</id>
    <parentid>371</parentid>
    <timestamp>2016-01-10T19:42:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="110" xml:space="preserve">[[Has type::Text]] [[Has description::Simple descriptive explanatory text property.]] [[Category:Lorem ipsum].</text>
    <sha1>75b4cf70ed786d248496f5ed497c5100e7261808</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Property:Has date</title>
  <ns>102</ns>
  <id>163</id>
  <revision>
    <id>373</id>
    <timestamp>2016-01-10T19:44:03Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Date]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Date]].</text>
    <sha1>5263c8921631f25051f416df19a72490a588561e</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:LinkToValue</title>
  <ns>10</ns>
  <id>164</id>
  <revision>
    <id>374</id>
    <timestamp>2016-01-10T19:49:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "LinkToValue" template. It should be called in the following format: &lt;pre&gt; {{LinkToValue }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="226" xml:space="preserve">&lt;noinclude&gt;
This is the "LinkToValue" template.
It should be called in the following format:
&lt;pre&gt;
{{LinkToValue
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>7468eb2c83076b2d61c92563072f470033afc339</sha1>
  </revision>
  <revision>
    <id>375</id>
    <parentid>374</parentid>
    <timestamp>2016-01-10T19:49:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="74" xml:space="preserve">&lt;includeonly&gt;{{{value}}}{{#if: {{{last-element|}}} | | · }}&lt;/includeonly&gt;</text>
    <sha1>3b850c37308305c7253a10ec70699f09e7d3275f</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:LinkToAskQueryForParameter</title>
  <ns>10</ns>
  <id>165</id>
  <revision>
    <id>376</id>
    <timestamp>2016-01-10T19:50:52Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "LinkToAskQueryForParameter" template. It should be called in the following format: &lt;pre&gt; {{LinkToAskQueryForParameter }} &lt;/pre&gt; Edit the page to see t..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="256" xml:space="preserve">&lt;noinclude&gt;
This is the "LinkToAskQueryForParameter" template.
It should be called in the following format:
&lt;pre&gt;
{{LinkToAskQueryForParameter
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>389b53f6cfcd0f3a74842044b5a8dfedd5277977</sha1>
  </revision>
  <revision>
    <id>377</id>
    <parentid>376</parentid>
    <timestamp>2016-01-10T19:51:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">&lt;includeonly&gt;{{#ask:
 [[{{{property}}}::{{{value}}}]]
 | limit=0
 | searchlabel={{{value}}}
}}{{#if: {{{last-element|}}} | | · }}&lt;/includeonly&gt;</text>
    <sha1>4733f2750123a93867df89f4afc69670d9ca878b</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:SetValue</title>
  <ns>10</ns>
  <id>166</id>
  <revision>
    <id>378</id>
    <timestamp>2016-01-10T19:52:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "SetValue" template. It should be called in the following format: &lt;pre&gt; {{SetValue }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;inclu..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="220" xml:space="preserve">&lt;noinclude&gt;
This is the "SetValue" template.
It should be called in the following format:
&lt;pre&gt;
{{SetValue
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>3a7bba8ab5dff91f6efea8bcd3fbc24e8ad1deb1</sha1>
  </revision>
  <revision>
    <id>379</id>
    <parentid>378</parentid>
    <timestamp>2016-01-10T19:53:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38" xml:space="preserve">&lt;includeonly&gt;{{{value}}}&lt;/includeonly&gt;</text>
    <sha1>6364f0d6b585c78ac641f25839ba4e653881678a</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:SetParserValue</title>
  <ns>10</ns>
  <id>167</id>
  <revision>
    <id>380</id>
    <timestamp>2016-01-10T19:54:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "SetParserValue" template. It should be called in the following format: &lt;pre&gt; {{SetParserValue }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noin..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="232" xml:space="preserve">&lt;noinclude&gt;
This is the "SetParserValue" template.
It should be called in the following format:
&lt;pre&gt;
{{SetParserValue
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>0ca2b87be9120b253093a6c79b7034eb6a4ed3f2</sha1>
  </revision>
  <revision>
    <id>381</id>
    <parentid>380</parentid>
    <timestamp>2016-01-10T19:54:47Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="73" xml:space="preserve">&lt;includeonly&gt;{{{value}}}{{#if: {{{last-element|}}} | | : }}&lt;/includeonly&gt;</text>
    <sha1>286095058907ec34a62676e2685ad16f8504021c</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:SetParserForValueInclusion</title>
  <ns>10</ns>
  <id>168</id>
  <revision>
    <id>382</id>
    <timestamp>2016-01-10T19:55:22Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "SetParserForValueInclusion" template. It should be called in the following format: &lt;pre&gt; {{SetParserForValueInclusion }} &lt;/pre&gt; Edit the page to see t..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="256" xml:space="preserve">&lt;noinclude&gt;
This is the "SetParserForValueInclusion" template.
It should be called in the following format:
&lt;pre&gt;
{{SetParserForValueInclusion
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>977ac67fb9919a9d435eb4f41d9df50ea6733745</sha1>
  </revision>
  <revision>
    <id>383</id>
    <parentid>382</parentid>
    <timestamp>2016-01-10T19:56:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="72" xml:space="preserve">&lt;includeonly&gt;{{{value}}}{{#if: {{{last-element|}}} | |,}} &lt;/includeonly&gt;</text>
    <sha1>4f4b44e96a7ad0b0e56c8b776478de4a117c2f98</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:Multi</title>
  <ns>10</ns>
  <id>169</id>
  <revision>
    <id>384</id>
    <timestamp>2016-01-10T19:57:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Multi" template. It should be called in the following format: &lt;pre&gt; {{Multi }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;includeonly..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="214" xml:space="preserve">&lt;noinclude&gt;
This is the "Multi" template.
It should be called in the following format:
&lt;pre&gt;
{{Multi
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>3faeb9984ab89b1428f229f089f5ca29be73cf98</sha1>
  </revision>
  <revision>
    <id>385</id>
    <parentid>384</parentid>
    <timestamp>2016-01-10T19:58:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="34" xml:space="preserve">*{{{label|}}} - {{{result|}}} &lt;br&gt;</text>
    <sha1>fb4528f6b9a23e02d03b1db23654bc712b9ee24f</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:HoldsMulti</title>
  <ns>10</ns>
  <id>170</id>
  <revision>
    <id>386</id>
    <timestamp>2016-01-10T19:59:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "HoldsMulti" template. It should be called in the following format: &lt;pre&gt; {{HoldsMulti }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;i..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="224" xml:space="preserve">&lt;noinclude&gt;
This is the "HoldsMulti" template.
It should be called in the following format:
&lt;pre&gt;
{{HoldsMulti
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>4854ced93b343b97aab7589b5755ef803c2c1a8e</sha1>
  </revision>
  <revision>
    <id>387</id>
    <parentid>386</parentid>
    <timestamp>2016-01-10T20:00:01Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Replaced content with "{{{Multi|}}}"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12" xml:space="preserve">{{{Multi|}}}</text>
    <sha1>83130d09ddb222f0be29a51e300cc71495e7cda4</sha1>
  </revision>
</page>
<page arvcontinue="20160106090101|340">
  <title>Template:Show items</title>
  <ns>10</ns>
  <id>171</id>
  <revision>
    <id>388</id>
    <timestamp>2016-01-10T20:01:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Show items" template. It should be called in the following format: &lt;pre&gt; {{Show items }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;i..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="224" xml:space="preserve">&lt;noinclude&gt;
This is the "Show items" template.
It should be called in the following format:
&lt;pre&gt;
{{Show items
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>95e1fc7c3d269d097beac83b464d00605a1ed6c4</sha1>
  </revision>
  <revision>
    <id>389</id>
    <parentid>388</parentid>
    <timestamp>2016-01-10T20:02:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="300" xml:space="preserve">&lt;noinclude&gt;
This is the "Show items" template.
It should be called in the following format:
&lt;pre&gt;
{{Show items
|Property 1=
|Property 2=
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;
'''Property 1:''' {{{Property 1|}}}

'''Property 2:''' {{{Property 2|}}}
&lt;/includeonly&gt;</text>
    <sha1>afef2f35fbaf46d85fd801e8c28cb01dd40a1b49</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Template:Listpages</title>
  <ns>10</ns>
  <id>172</id>
  <revision>
    <id>390</id>
    <timestamp>2016-01-10T20:03:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Listpages" template. It should be called in the following format: &lt;pre&gt; {{Listpages }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;inc..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="222" xml:space="preserve">&lt;noinclude&gt;
This is the "Listpages" template.
It should be called in the following format:
&lt;pre&gt;
{{Listpages
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>97ec00beca83c8d528dabe46431582f56e48d071</sha1>
  </revision>
  <revision>
    <id>391</id>
    <parentid>390</parentid>
    <timestamp>2016-01-10T20:04:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="504" xml:space="preserve">&lt;includeonly&gt;
== Only the values ==
* {{{1|}}}
* &lt;big&gt;'''{{{2|}}}'''&lt;/big&gt;

== Increase decrease values ==
{{#autoedit:form=Test
|target=Valuetest
|link text=Increase
|link type=button
|query string=Test[value]={{#expr:{{#show:Valuetest|?Value}} + 1}}
|reload
}} &lt;--------&gt; {{#autoedit:form=Test
|target=Valuetest
|link text=Decrease
|link type=button
|query string=Test[value]={{#expr:{{#show:Valuetest|?Value}} - 1}}
|reload
}}

== Input box ==
&lt;inputbox&gt;
type=create
break=no
&lt;/inputbox&gt;&lt;/includeonly&gt;</text>
    <sha1>6269cb8e3907b8e011d9704c349d9e762b94a87b</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Blackbook</title>
  <ns>0</ns>
  <id>173</id>
  <revision>
    <id>392</id>
    <timestamp>2016-01-13T16:41:33Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;  &lt;html xmlns="..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="43538" xml:space="preserve">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;
 &lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us" dir=""&gt;
 &lt;head&gt;


    &lt;script type="text/javascript"&gt;var _starttime = new Date().getTime();&lt;/script&gt;
    &lt;meta http-equiv="Content-Type" content="text/html; charset=utf-8" /&gt;
    &lt;meta name="robots" content="index,follow" /&gt;
&lt;link rel="shortcut icon" href="favicon.ico" /&gt;
&lt;meta name="generator" content=" Wik.is" /&gt;
&lt;link rel="search" type="application/opensearchdescription+xml" title="Federal Data Web 2.0 Wiki Pilot Search" href="/@gui/opensearch/description" /&gt;    &lt;title&gt;Blackbook 2 and 3 - Federal Data Web 2.0 Wiki Pilot&lt;/title&gt;
    
    &lt;!-- default css --&gt;
    &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/fiesta/_reset.css"/&gt;
    &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/common/css.php" /&gt; &lt;!--[if IE 7]&gt;&lt;style type="text/css"&gt;@import "/skins/common/_ie7.css";&lt;/style&gt;&lt;![endif]--&gt;&lt;!--[if IE 6]&gt;&lt;style type="text/css"&gt;@import "/skins/common/_ie.css";&lt;/style&gt;&lt;![endif]--&gt;    &lt;link rel="stylesheet" type="text/css" media="print" href="skins/common/print.css" /&gt;    
    &lt;!-- default scripting --&gt;
    &lt;script type="text/javascript" src="skins/common/js.php?perms=LOGIN,BROWSE,READ,SUBSCRIBE&amp;amp;lang=en-us"&gt;&lt;/script&gt;    
    &lt;!-- specific screen stylesheets--&gt;
        &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/fiesta/sky-tangerine/css.php"/&gt;
        
    &lt;!-- specific print stylesheets --&gt;
    &lt;link rel="stylesheet" type="text/css" media="print" href="skins/fiesta/print.css" /&gt;
   
    &lt;!-- IE6 &amp; IE7 specific stuff --&gt;
    &lt;!--[if IE]&gt;&lt;meta http-equiv="imagetoolbar" content="no" /&gt;&lt;![endif]--&gt;
    &lt;!--[if IE 6]&gt;&lt;link rel="stylesheet" type="text/css" media="screen" href="/skins/fiesta/sky-tangerine/ie6.php"/&gt;&lt;![endif]--&gt;
    &lt;!--[if IE 7]&gt;&lt;link rel="stylesheet" type="text/css" media="screen" href="/skins/fiesta/sky-tangerine/ie7.php"/&gt;&lt;![endif]--&gt;
    
    	&lt;script type="text/javascript"&gt;

	    _page_redirect = false;
_path_tpl = '/skins/fiesta';
_path_skin = '/skins/fiesta/sky-tangerine';
_path_common = '/skins/common';
_path_icons = '/skins/common/icons';
editToken = 'f50e1eed8f38fedcfc02890ed226112a';
_userName = 'Anonymous';
_userId = '2';
var _editor_styles_path = ['/skins/fiesta/_editor.css', '/skins/fiesta/sky-tangerine/_content.css', ''];
_today = '2 Oct 2010';
baseHref = '/web/20101003032546/http://federaldata.Wik.is';
_page_titlePath = '/';
_page_titleName = 'Blackbook 2 and 3';
_page_ID = 710;
_total_images = 6;
contextTopic = 'Blackbook 2 and 3';
_over_storage_quota = false;
saveFlag = false;

	    
		// remote scripting library
		// (c) copyright 2005 modernmethod, inc
		var sajax_debug_mode = false;
		var sajax_request_type = "POST";

		function sajax_debug(text) {
			if (sajax_debug_mode)
				alert("RSD: " + text);
		};

		function sajax_init_object() {
			sajax_debug("sajax_init_object() called..");

			var A = window.XMLHttpRequest ? new XMLHttpRequest() : window.ActiveXObject ? new ActiveXObject("Microsoft.XMLHTTP") : null;
			if (!A)
				sajax_debug("Could not create connection object.");
			return A;
		};
		function _sajax_do_call(x, func_name, args) {
			var i, x, n;
			var uri;
			var post_data;

			uri = "/index.php";
			if (sajax_request_type == "GET") {
				if (uri.indexOf("?") == -1) 
					uri = uri + "?rs=" + encodeURIComponent(func_name);
				else
					uri = uri + "&amp;rs=" + encodeURIComponent(func_name);
				for (i = 0; i &lt; args.length-1; i++) {
				    var a = args[i];
					uri = uri + "&amp;rsargs[]=" + encodeURIComponent(a);
				}
				uri = uri + "&amp;rsrnd=" + new Date().getTime();
				post_data = null;
			} else {
				post_data = "rs=" + func_name;
				for (i = 0; i &lt; args.length-1; i++) {
				    var a = args[i];
					post_data = post_data + "&amp;rsargs[]=" + encodeURIComponent(a);
				}
			}
			x.open(sajax_request_type, uri, true);
			if (sajax_request_type == "POST") {
				x.setRequestHeader("Method", "POST " + uri + " HTTP/1.1");
				x.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
			}
			x.onreadystatechange = function() {
				if (x.readyState != 4) 
					return;
				if (typeof sajax_debug != 'undefined') sajax_debug("received " + x.responseText);

				var status;
				var data = x.responseText.replace(/^\s+/, '');
				status = data.charAt(0);
				data = data.substring(2);
				if (status == "-") 
					alert("Error: " + data);
				else  
					args[args.length-1](data);
			}
			x.send(post_data);
			sajax_debug(func_name + " uri = " + uri + "/post = " + post_data);
			sajax_debug(func_name + " waiting..");
			return x;
		};
		function sajax_do_call(func_name, args) {
			x = sajax_init_object();
			_sajax_do_call(x, func_name, args);
			delete x;
		};

		function x_breadcrumbSet() { sajax_do_call("breadcrumbSet", x_breadcrumbSet.arguments); };
		function x_wfAdminUserForm() { sajax_do_call("wfAdminUserForm", x_wfAdminUserForm.arguments); };
		function x_wfSetUserOption() { sajax_do_call("wfSetUserOption", x_wfSetUserOption.arguments); };
		function x_wfSetRestrictions() { sajax_do_call("wfSetRestrictions", x_wfSetRestrictions.arguments); };
		function x_setUserOption() { sajax_do_call("setUserOption", x_setUserOption.arguments); };
		function x_wfValidateUserOrGroup() { sajax_do_call("wfValidateUserOrGroup", x_wfValidateUserOrGroup.arguments); };
		function x_wfSaveEdit() { sajax_do_call("wfSaveEdit", x_wfSaveEdit.arguments); };
		function x_wfQueryLinks() { sajax_do_call("wfQueryLinks", x_wfQueryLinks.arguments); };
		function x_loadInplaceEditor() { sajax_do_call("loadInplaceEditor", x_loadInplaceEditor.arguments); };
		function x_doSetbaseHref() { sajax_do_call("doSetbaseHref", x_doSetbaseHref.arguments); };
		function x_showFileAttachments() { sajax_do_call("showFileAttachments", x_showFileAttachments.arguments); };
		function x_doSectionEdit() { sajax_do_call("doSectionEdit", x_doSectionEdit.arguments); };
		function x_postComment() { sajax_do_call("postComment", x_postComment.arguments); };
		function x_getComments() { sajax_do_call("getComments", x_getComments.arguments); };
		function x_deleteComment() { sajax_do_call("deleteComment", x_deleteComment.arguments); };
		function x_editComment() { sajax_do_call("editComment", x_editComment.arguments); };
		function x_wfEmailPage() { sajax_do_call("wfEmailPage", x_wfEmailPage.arguments); };
		function x_wfCheckNewTitle() { sajax_do_call("wfCheckNewTitle", x_wfCheckNewTitle.arguments); };
		function x_wfDeleteFile() { sajax_do_call("wfDeleteFile", x_wfDeleteFile.arguments); };
		function x_wfSetPageProperties() { sajax_do_call("wfSetPageProperties", x_wfSetPageProperties.arguments); };
		function x_wfDeleteTopic() { sajax_do_call("wfDeleteTopic", x_wfDeleteTopic.arguments); };
		function x_wfRenameTopic() { sajax_do_call("wfRenameTopic", x_wfRenameTopic.arguments); };
		function x_wfMoveAttachments() { sajax_do_call("wfMoveAttachments", x_wfMoveAttachments.arguments); };
		function x_wfGetAttachmentUrl() { sajax_do_call("wfGetAttachmentUrl", x_wfGetAttachmentUrl.arguments); };
		function x_wfInlineImageGallery() { sajax_do_call("wfInlineImageGallery", x_wfInlineImageGallery.arguments); };
		function x_wfSetFileDescription() { sajax_do_call("wfSetFileDescription", x_wfSetFileDescription.arguments); };
		function x_wfChangeLoginView() { sajax_do_call("wfChangeLoginView", x_wfChangeLoginView.arguments); };
		function x_wfChangeLoginViewToCreate() { sajax_do_call("wfChangeLoginViewToCreate", x_wfChangeLoginViewToCreate.arguments); };
		function x_wfSaveCredsToSession() { sajax_do_call("wfSaveCredsToSession", x_wfSaveCredsToSession.arguments); };
		function x_wfChangeAddServiceView() { sajax_do_call("wfChangeAddServiceView", x_wfChangeAddServiceView.arguments); };
		function x_wfSaveLoginPageCreds() { sajax_do_call("wfSaveLoginPageCreds", x_wfSaveLoginPageCreds.arguments); };
		function x_wfRemindPassword() { sajax_do_call("wfRemindPassword", x_wfRemindPassword.arguments); };
		function x_wfChangeAvailUsersPage() { sajax_do_call("wfChangeAvailUsersPage", x_wfChangeAvailUsersPage.arguments); };
		
	    window.onbeforeunload = checkForChanges;

	    function checkForChanges() {
	        if (saveFlag &amp;&amp; !doCheckChanges(cur_editor)) {
	        	return "You have made changes to the content without saving your changes. Are you sure you want to exit this page?";
	        }
	    }
	    var aLt = new Array();aLt["attach-no-description"] = 'No description'; aLt["cancel"] = 'Cancel'; aLt["comment-delete"] = 'Are you sure you want to delete this comment?'; aLt["gallery-close"] = 'close'; aLt["gallery-next"] = 'next'; aLt["gallery-prev"] = 'prev'; aLt["internal-error"] = 'Sorry, but there was an internal problem - please try again soon.'; aLt["js-label_cancel"] = 'Cancel'; aLt["js-label_save"] = 'Save'; aLt["js-tooltip_cancel"] = 'Exit Without Saving Changes'; aLt["js-tooltip_save"] = 'Save and Exit (Alt+S)'; aLt["ldap-provide-credentials"] = 'Please provide external service login credentials.'; aLt["loading"] = 'Loading...'; aLt["menu-confirm-delete"] = 'Are you sure you want to delete this file?'; aLt["menu-delete-file"] = 'Delete'; aLt["menu-edit-description"] = 'Edit description'; aLt["menu-move-file"] = 'Move'; aLt["menu-previous-versions"] = 'Previous versions'; aLt["menu-view-original"] = 'View original'; aLt["print-end-notes"] = 'Endnotes'; aLt["ready"] = 'Ready'; aLt["submit"] = 'Submit'; aLt["select-files"] = 'Select files...'; aLt["wikibits-attach-another"] = 'Attach another file'; aLt["wikibits-attach-file"] = 'Attach File'; aLt["wikibits-cant-attach-editing"] = 'Sorry, you can\'t attach files while editing a page. Please close the editor first.'; aLt["wikibits-edit-section"] = 'Edit section'; aLt["wikibits-remove-file"] = 'Remove file';  var wfMsg = function (key) { return aLt[key] ? aLt[key] : 'MISSING: ' + key; };var navMaxWidth = 1600;
	//hook in menu clicking events to the document's body
	YAHOO.util.Event.addListener(document, "click", function () { FileMenu.bodyClick(); DWMenu.BodyClick(); });	
	YAHOO.util.Event.onDOMReady(function () { new clientWindow }); 
	
                
		YAHOO.util.Event.onAvailable("siteNavTree", wik.nav.init, wik.nav, true);
		
	
			YAHOO.util.Event.onDOMReady(function() {
			tb_init('a.lightbox, area.lightbox, input.lightbox, a[@rel=awesomebox]');//pass where to apply thickbox
			imgLoader = new Image();// preload image
			imgLoader.src = tb_pathToImage;
		});
		
		YAHOO.util.Event.onDOMReady(function() { 
			MTComments.HookBehavior();
		});
		&lt;/script&gt;
	
	&lt;!-- styles overwritten via control panel - load this css last --&gt;	
	 
&lt;/head&gt;

&lt;body class="  en-us"&gt;


&lt;noscript&gt;This application requires Javascript to be enabled.&lt;/noscript&gt;

&lt;div class="global"&gt;
	&lt;div class="globalWrap"&gt;
		&lt;div class="header"&gt;
		
			&lt;div class="mastPre"&gt;&lt;/div&gt;
			&lt;div class="mast"&gt;
				
				&lt;div class="siteLogo"&gt;
					&lt;a href="" title="Federal Data Web 2.0 Wiki Pilot"&gt;&lt;img src="skins/fiesta/sky-tangerine/logo.png" alt="Federal Data Web 2.0 Wiki Pilot" title="Federal Data Web 2.0 Wiki Pilot"/&gt;&lt;/a&gt;		
				&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="mastPost"&gt;&lt;/div&gt;
			
			&lt;div class="siteNavPre"&gt;&lt;/div&gt;
			&lt;div class="siteNav"&gt;
				&lt;div class="userAuthPre"&gt;&lt;/div&gt;
							&lt;div class="userAuth"&gt;
			&lt;span&gt;Logged in:&lt;/span&gt;			&lt;span&gt;Logged in as:&lt;/span&gt;					
	 		&lt;a href="index.php?title=Special:Userlogin&amp;amp;returntotitle=Blackbook+2+and+3" class="userLogin"&gt;Log in&lt;/a&gt;		&lt;/div&gt;
						
									&lt;div class="userAuthPost"&gt;&lt;/div&gt;
				
				&lt;div class="custom custom2"&gt;
									&lt;/div&gt;
				
					
				&lt;div class="navPre"&gt;&lt;/div&gt;
					&lt;div id="siteNavTree"&gt;&lt;div class="node dockedNode homeNode lastDocked parentClosed" id="n21" c="n2348,n710,n70,n542,n497,n1144,n702,n2349,n1437,n2346,n990,n35,n33,n34,n526,n543,n1884,n46,n842,n498,n418,n75,n73,n654,n1883,n534,n2368,n704,n661,n653,n711,n1473,n2352,n427,n1140,n2287,n581,n695,n1935,n1134,n500,n2359,n1757" path=""&gt;&lt;a href="" title="Federal Data Web 2.0 Wiki Pilot"&gt;&lt;span&gt;Federal Data Web 2....&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n2348" p="n21" path="Analytics/"&gt;&lt;a href="Analytics" title="Analytics"&gt;&lt;span&gt;Analytics&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling selected" id="n710" p="n21" path="Blackbook_2_and_3/"&gt;&lt;a href="Blackbook_2_and_3" title="Blackbook 2 and 3"&gt;&lt;span&gt;Blackbook 2 and 3&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n70" p="n21" path="Blog_(Web_Log)/"&gt;&lt;a href="Blog_(Web_Log)" title="Blog (Web Log)"&gt;&lt;span&gt;Blog (Web Log)&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n542" p="n21" path="Cambridge_Semantics_Recovery.gov/"&gt;&lt;a href="Cambridge_Semantics_Recovery.gov" title="Cambridge Semantics Recovery.gov"&gt;&lt;span&gt;Cambridge Semantic...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n497" p="n21" path="Comments_and_Innovations_for_the_Open_Government_and_Transparency_Directive/"&gt;&lt;a href="Comments_and_Innovations_for_the_Open_Government_and_Transparency_Directive" title="Comments and Innovations for the Open Government and Transparency Directive"&gt;&lt;span&gt;Comments and Innov...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1144" p="n21" path="Data.gov/"&gt;&lt;a href="Data.gov" title="Data.gov Adds Geoviewer"&gt;&lt;span&gt;Data.gov Adds Geovi...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n702" p="n21" path="Data.gov_Concept_of_Operations_v0.7/"&gt;&lt;a href="Data.gov_Concept_of_Operations_v0.7" title="Data.gov Concept of Operations"&gt;&lt;span&gt;Data.gov Concept of...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n2349" p="n21" path="Data.gov_CONOPS/"&gt;&lt;a href="Data.gov_CONOPS" title="Data.gov CONOPS"&gt;&lt;span&gt;Data.gov CONOPS&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1437" p="n21" path="Data.gov%2fsemantic/"&gt;&lt;a href="Data.gov%2f%2fsemantic" title="Data.gov/semantic"&gt;&lt;span&gt;Data.gov/semantic&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n2346" p="n21" path="Data_Science/" cd="0"&gt;&lt;a href="Data_Science" title="Data Science"&gt;&lt;span&gt;Data Science&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n990" p="n21" path="Executive_Office_of_the_President_-_OMB_and_NSA_Detail/"&gt;&lt;a href="Executive_Office_of_the_President_-_OMB_and_NSA_Detail" title="Executive Office of the President - OMB and NSA Detail for Data.gov"&gt;&lt;span&gt;Executive Office of ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n35" p="n21" path="Federal_Data_Architecture_Subcommittee_(DAS)/" cd="0"&gt;&lt;a href="Federal_Data_Architecture_Subcommittee_(DAS)" title="Federal Data Architecture Subcommittee (DAS)"&gt;&lt;span&gt;Federal Data Archite...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n33" p="n21" path="Federal_Data_Reference_Model/"&gt;&lt;a href="Federal_Data_Reference_Model" title="Federal Data Reference Model"&gt;&lt;span&gt;Federal Data Refere...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n34" p="n21" path="Federal_Data_Reference_Model_2.0/" cd="0"&gt;&lt;a href="Federal_Data_Reference_Model_2.0" title="Federal Data Reference Model 2.0"&gt;&lt;span&gt;Federal Data Refere...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n526" p="n21" path="Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form/" cd="0"&gt;&lt;a href="Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form" title="Federal Enterprise Architecture Reference Model Revision Submission Form (DRM 3.0)"&gt;&lt;span&gt;Federal Enterprise A...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n543" p="n21" path="Federal_Enterprise_Architecture_Security_and_Privacy_Profile_Version_3.0/" cd="0"&gt;&lt;a href="Federal_Enterprise_Architecture_Security_and_Privacy_Profile_Version_3.0" title="Federal Enterprise Architecture Security and Privacy Profile Version 3.0"&gt;&lt;span&gt;Federal Enterprise A...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1884" p="n21" path="Federal_IT_Dashboard/"&gt;&lt;a href="Federal_IT_Dashboard" title="Federal IT Dashboard"&gt;&lt;span&gt;Federal IT Dashboar...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n46" p="n21" path="Federal_Semantic_Interoperability_Community_of_Practice_(SICoP)/" cd="0"&gt;&lt;a href="Federal_Semantic_Interoperability_Community_of_Practice_(SICoP)" title="Federal Semantic Interoperability Community of Practice (SICoP)"&gt;&lt;span&gt;Federal Semantic Int...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n842" p="n21" path="FGDC_Standards_WG_meeting_-_February_23,_2010/"&gt;&lt;a href="FGDC_Standards_WG_meeting_-_February_23%2c_2010" title="FGDC Standards WG Meeting - February 23, 2010"&gt;&lt;span&gt;FGDC Standards WG ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n498" p="n21" path="George_Thomas_on_Recovery.gov/"&gt;&lt;a href="George_Thomas_on_Recovery.gov" title="George Thomas on Recovery.gov"&gt;&lt;span&gt;George Thomas on R...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n418" p="n21" path="Harnessing_the_Power_of_Digital_Data_for_Science_and_Society/" cd="0"&gt;&lt;a href="Harnessing_the_Power_of_Digital_Data_for_Science_and_Society" title="Harnessing the Power of Digital Data for Science and Society"&gt;&lt;span&gt;Harnessing the Powe...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n75" p="n21" path="Interagency_Forum_on_Data_Preservation,_Stewardship,_and_LifeCycle_ESIP_Federation_Meeting,_January_8,_2009/"&gt;&lt;a href="Interagency_Forum_on_Data_Preservation%2c_Stewardship%2c_and_LifeCycle_ESIP_Federation_Meeting%2c_January_8%2c_2009" title="Interagency Forum on Data Preservation, Stewardship, and LifeCycle ESIP Federation Meeting, January 8, 2009"&gt;&lt;span&gt;Interagency Forum o...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n73" p="n21" path="Interagency_Working_Group_on_Digitial_Data/" cd="0"&gt;&lt;a href="Interagency_Working_Group_on_Digitial_Data" title="Interagency Working Group on Digitial Data"&gt;&lt;span&gt;Interagency Working...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n654" p="n21" path="June_4,_2009_How_Does_Government_Become_an_Open_Platform?/"&gt;&lt;a href="June_4%2c_2009_How_Does_Government_Become_an_Open_Platform%3f" title="June 4, 2009 How Does Government Become an Open Platform?"&gt;&lt;span&gt;June 4, 2009 How Do...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1883" p="n21" path="Labor's_Enforcement_Data_Catalog/"&gt;&lt;a href="Labor's_Enforcement_Data_Catalog" title="Labor's Enforcement Data Catalog"&gt;&lt;span&gt;Labor's Enforcement...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling moreNodes" id="n534" p="n21" path="May_13,_2009_Semantic_Web_Meetup/" content="May 13, 2009 Seman..." contentTitle="May 13, 2009 Semantic Web Meetup" hiddenNodes="n2368,n704,n661,n653,n711,n1473,n2352,n427,n1140,n2287,n581,n695,n1935,n1134,n500,n2359,n1757"&gt;&lt;a href="May_13%2c_2009_Semantic_Web_Meetup" title="More..."&gt;&lt;span class="more"&gt;...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2368" p="n21" path="Model_for_Performance-Driven_Government/" cd="0"&gt;&lt;a href="Model_for_Performance-Driven_Government" title="Model for Performance-Driven Government"&gt;&lt;span&gt;Model for Performan...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n704" p="n21" path="NIEM/"&gt;&lt;a href="NIEM" title="NIEM"&gt;&lt;span&gt;NIEM&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n661" p="n21" path="Open_Group_Enterprise_Vocabularly_Workshop_June_3,_2009/"&gt;&lt;a href="Open_Group_Enterprise_Vocabularly_Workshop_June_3%2c_2009" title="Open Group Enterprise Vocabularly Workshop June 3, 2009"&gt;&lt;span&gt;Open Group Enterpri...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n653" p="n21" path="Open_Group_Enterprise_Vocabulary_Workshop_May_20,_2009/"&gt;&lt;a href="Open_Group_Enterprise_Vocabulary_Workshop_May_20%2c_2009" title="Open Group Enterprise Vocabulary Workshop May 20, 2009"&gt;&lt;span&gt;Open Group Enterpri...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n711" p="n21" path="Page_Title/"&gt;&lt;a href="Page_Title" title="Open Government Directive Workshop, January 11, 2010"&gt;&lt;span&gt;Open Government Di...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1473" p="n21" path="Scientific_Data_Management_for_Government_Agencies/"&gt;&lt;a href="Scientific_Data_Management_for_Government_Agencies" title="Scientific Data Management for Government Agencies"&gt;&lt;span&gt;Scientific Data Mana...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2352" p="n21" path="Semantic_eScience/" cd="0"&gt;&lt;a href="Semantic_eScience" title="Semantic eScience"&gt;&lt;span&gt;Semantic eScience&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n427" p="n21" path="Statistical_Abstract_of_the_United_States:_2009/" cd="0"&gt;&lt;a href="Statistical_Abstract_of_the_United_States%3a_2009" title="Statistical Abstract of the United States: 2009"&gt;&lt;span&gt;Statistical Abstract ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n1140" p="n21" path="Statistics/" cd="0"&gt;&lt;a href="Statistics" title="Statistics"&gt;&lt;span&gt;Statistics&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2287" p="n21" path="Survey_of_EPA_and_Other_Federal_Agency_Scientific_Data_Management_Policies_and_Guidance_2010/" cd="0"&gt;&lt;a href="Survey_of_EPA_and_Other_Federal_Agency_Scientific_Data_Management_Policies_and_Guidance_2010" title="Survey of EPA and Other Federal Agency Scientific Data Management Policies and Guidance 2010"&gt;&lt;span&gt;Survey of EPA and O...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n581" p="n21" path="The_Recovery_Dialogue_on_IT_Solutions/" cd="0"&gt;&lt;a href="The_Recovery_Dialogue_on_IT_Solutions" title="The Recovery Dialogue on IT Solutions"&gt;&lt;span&gt;The Recovery Dialog...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n695" p="n21" path="Tools_for_linked_data_from_DERI/"&gt;&lt;a href="Tools_for_linked_data_from_DERI" title="Tools for linked data from DERI"&gt;&lt;span&gt;Tools for linked dat...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1935" p="n21" path="Top_Secret_America/"&gt;&lt;a href="Top_Secret_America" title="Top Secret America"&gt;&lt;span&gt;Top Secret America&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n1134" p="n21" path="Ucore-SL/" cd="0"&gt;&lt;a href="Ucore-SL" title="Ucore-SL"&gt;&lt;span&gt;Ucore-SL&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n500" p="n21" path="W3C_eGovernment_Interest_Group/" cd="0"&gt;&lt;a href="W3C_eGovernment_Interest_Group" title="W3C eGovernment Interest Group"&gt;&lt;span&gt;W3C eGovernment In...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n2359" p="n21" path="Watershed_Boundary_Dataset/"&gt;&lt;a href="Watershed_Boundary_Dataset" title="Watershed Boundary Dataset"&gt;&lt;span&gt;Watershed Boundary ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1757" p="n21" path="White_House_Salaries/"&gt;&lt;a href="White_House_Salaries" title="White House Salaries"&gt;&lt;span&gt;White House Salarie...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;				&lt;div class="navPost"&gt;&lt;/div&gt;
					
				&lt;div class="custom"&gt;
									&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="siteNavPost"&gt;&lt;/div&gt;
		&lt;/div&gt;
				
		&lt;div class="body"&gt;
			&lt;div class="bodyHeader"&gt;
				&lt;div class="pre"&gt;&lt;/div&gt;
				&lt;div class="post"&gt;&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="page"&gt;
				&lt;!-- required print options --&gt;
								
				&lt;div class="custom custom1"&gt;
								&lt;/div&gt;
				
				&lt;div class="siteNav"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
						
	&lt;div class="siteSearch"&gt;
		&lt;fieldset class="search"&gt;
	 		&lt;form action="Special:Search"&gt;
		        &lt;span&gt;Search: &lt;/span&gt;&lt;input id="searchInput" class="inputText" name="search" type="text" value="" /&gt;
				&lt;input type="hidden" name="type" value="fulltext" /&gt;
		        &lt;input type="submit" name="go" class="inputSubmit" value="Find" /&gt;
			&lt;/form&gt;
		&lt;/fieldset&gt;
	&lt;/div&gt;
					
					&lt;ul&gt;
						&lt;li class="userPage"&gt;&lt;a href="User:Anonymous"&gt;&lt;span&gt;&lt;/span&gt;My Page&lt;/a&gt;&lt;/li&gt;
												&lt;li class="siteChanges"&gt;&lt;a href="Special:Recentchanges"&gt;&lt;span&gt;&lt;/span&gt;Recent changes&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteTools"&gt;&lt;a href="#" onclick="return DWMenu.Position('menuTools', this, 0, 0);"&gt;&lt;span&gt;&lt;/span&gt;Tools&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteHelp"&gt;&lt;a href="Resources/Documentation/FAQ/MindTouch_Express"&gt;&lt;span&gt;&lt;/span&gt;Help&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteHelp"&gt;&lt;a href="pro/"&gt;&lt;span&gt;&lt;/span&gt;Go Pro&lt;/a&gt;&lt;/li&gt;					&lt;/ul&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="pageBar"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
					&lt;div class="pageRevision"&gt;
						&lt;!-- last modified --&gt;
						Page last modified &lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=history" title="20:27, 15 Feb 2010"&gt;20:27, 15 Feb 2010&lt;/a&gt; by &lt;a href="User:LucasGraim" class="link-user" rel="internal"&gt;LucasGraim&lt;/a&gt;						&lt;!-- end last modified --&gt;					
					&lt;/div&gt;
					&lt;div class="pageNav"&gt;
						&lt;ul&gt;
							&lt;li class="pageEdit"&gt;&lt;a href="#" title="Edit page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Edit page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageAdd"&gt;&lt;a href="#" title="New page" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;New page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageRestrict"&gt;&lt;a href="#" title="Restrict access" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Restrict access&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageAttach"&gt;&lt;a href="#" title="Attach file" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Attach file&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageMove"&gt;&lt;a href="#" title="Move page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Move page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageDelete"&gt;&lt;a href="#" title="Delete page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Delete page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pagePrint"&gt;&lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=print" title="Print page" onclick="return Print.open('/index.php?title=Blackbook_2_and_3&amp;amp;action=print');" class=""&gt;&lt;span&gt;&lt;/span&gt;Print page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageMore"&gt;&lt;a href="#" onclick="return DWMenu.Position('menuPageOptions', this, 0, 0);"&gt;&lt;span&gt;&lt;/span&gt;More&lt;/a&gt;&lt;/li&gt;
							&lt;li class="navSplit"&gt;&lt;/li&gt;
							&lt;li class="pageToc"&gt;&lt;a href="#" title="Table of contents" onclick="return DWMenu.Position('menuPageContent', this, -2, 0)" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Table of contents&lt;/a&gt;&lt;/li&gt;
						&lt;/ul&gt;
					&lt;/div&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="pageContentFrame"&gt;
				&lt;div class="custom custom4"&gt;
								&lt;/div&gt;
				
				&lt;div id="pageContent" class="pageContent"&gt;
							 				&lt;div class="hierarchy"&gt;
		 					&lt;span class="dw-hierarchy"&gt;&lt;a href=""&gt;Federal Data Web 2.0 Wiki Pilot&lt;/a&gt; &amp;gt; Blackbook 2 and 3&lt;/span&gt;		 				&lt;/div&gt;
	 								
										&lt;div class="pageTitle"&gt;
												&lt;h1 id="title"&gt;&lt;span  class="pageRestricted" &gt;Blackbook 2 and 3&lt;/span&gt;&lt;/h1&gt;
					&lt;/div&gt;
					
								
					&lt;div class="pageStatus"&gt;
 					     					&lt;/div&gt;
 					
 							
					&lt;div class="PageDW-Blackbook2and3"&gt;								
	 				&lt;div id="page-top"&gt;&lt;div id="pageToc"&gt;&lt;div class="pageToc"&gt;&lt;h5&gt;Table of contents&lt;/h5&gt;&lt;em&gt;No headers&lt;/em&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="pageText" id="pageText"&gt; &lt;p&gt;NSA&amp;rsquo;s Blackbook 2 and 3 - The Standard in Semantic Web Technology for Data Management:&lt;/p&gt; &lt;p&gt;Blackbook2 is a project architected by Intervise&amp;rsquo;s Chief Technology Officer (Scott Streit), which moved into open source on September 1, 2009. Blackbook2 is a standard for semantic web processing and is currently used, in production or pilots, at the Department of Defense, Dole Foods, and the Environmental Protection Agency, just to name a few. Without changing Blackbook2, merely adding new data, Blackbook2 processes anything from Shipping Visibility Data to classified, analytical processing.&lt;/p&gt; &lt;p&gt;For &lt;a class=" external" rel="external nofollow" target="_blank" href="" title="http://www.resumesplanet.com"&gt; resume writers&lt;/a&gt;, web application framework for data analysis, Blackbook2's architecture provides secure support for visualization, transformation, data source integration, asynchronous operations, and is vocabulary agnostic. Application programming interfaces (APIs) exist for plugin components that visualize, discover, transform, extract, enrich, or filter graph&amp;#8208;based data such as social networks. Data sources of many types (RDBMs, Documents, RSS) can be mapped into Blackbook2 as RDF/OWL, either by Ingest or real-time mapping solutions such as D2RQ.&lt;/p&gt; &lt;p&gt;The Blackbook2 architecture provides asynchronous operations via a message bus backend so that results are provided just-in-time to real&amp;#8208;time users or to workflows that may run for hours. Blackbook2 is vocabulary agnostic: it can provide mapping to a common ontology for all data sources or it can accommodate disparate vocabularies with common vocabulary subsets (e.g., Dublin Core, VCard). Finally, Blackbook2 is accredited for multi-level security via role-based access and provides integrated logging via standard interfaces (JAAS and Log4J).&lt;/p&gt; &lt;p&gt;Blackbook 2, and now 3, is available free to Federal government employees and is currently running on the NSA CloudBase Cloud Computing Platform. Software, documentation, and collaboration are available at &lt;a class="external" rel="external nofollow" target="_blank" href="wiki/index.php/Main_Page" title="http://rabasrv.jhuapl.edu/wiki/index.php/Main_Page"&gt;http://rabasrv.jhuapl.edu/wiki/index.php/Main_Page&lt;/a&gt;&amp;nbsp; by contacting Buster Fields at &lt;a class="link-mailto" rel="external nofollow" target="_blank" href="mailto:hlfield@nsa.gov" title="mailto:hlfield@nsa.gov"&gt;hlfield@nsa.gov&lt;/a&gt; .&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="printfooter" id="printfooter"&gt;&lt;hr /&gt;
&lt;p&gt;Retrieved from "&lt;a href="Blackbook_2_and_3"&gt;http://federaldata.Wik.is/Blackbook_2_and_3&lt;/a&gt;"&lt;/p&gt;
&lt;/div&gt;
	 				&lt;/div&gt;
				&lt;/div&gt;
				&lt;/div&gt;
				&lt;div class="DW-clear"&gt;&lt;/div&gt;
								&lt;div class="pageInfo"&gt;
					&lt;dl&gt;
						&lt;dt class="pageTags"&gt;&lt;span&gt;&lt;/span&gt;Tag page&lt;/dt&gt;
						&lt;dd class="pageTags"&gt;
			 				&lt;div id="pageTags"&gt;&lt;div class="pageTagList"&gt;&lt;div class="item taglist"&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;		 				&lt;/dd&gt;
						
						&lt;dt class="pageIncomingLinks"&gt;&lt;span&gt;&lt;/span&gt;What links here&lt;/dt&gt;
						&lt;dd class="pageIncomingLinks"&gt;&lt;/dd&gt;
					&lt;/dl&gt;
				&lt;/div&gt;
				
								
				&lt;div class="file"&gt;
					&lt;h2&gt;Files 0&lt;/h2&gt;
					&lt;div class="fileAdd"&gt;
						&lt;a href="Blackbook_2_and_3" class="disabled" onclick="return false"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="attach" alt="" /&gt;&lt;/span&gt;&lt;span class="text"&gt;Attach file or image&lt;/span&gt;&lt;/a&gt;					&lt;/div&gt;
					&lt;div class="fileList"&gt;
		 				&lt;div id="pageFiles"&gt;&lt;div class="nofiles"&gt;&amp;nbsp;&lt;/div&gt;&lt;/div&gt;					&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="gallery"&gt;
					&lt;h2&gt;Images 0&lt;/h2&gt;
	 				&lt;div id="pageGalleryWrap"&gt;&lt;div class="nofiles"&gt;&amp;nbsp;&lt;/div&gt;&lt;/div&gt;				&lt;/div&gt;
				
 				&lt;div id="comments"&gt;&lt;div class="comments"&gt;&lt;div class="commentMore"&gt;Viewing 15 of 143 comments: &lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;commentcount=all#comments" onclick="return MTComments.GetComments('all');" id="commentViewAll"&gt;view all&lt;/a&gt;&lt;/div&gt;&lt;div class="comment" id="comment179"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment179"&gt;#179&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm179"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText179"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment177"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment177"&gt;#177&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm177"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText177"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment176"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment176"&gt;#176&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm176"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText176"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment184"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment184"&gt;#184&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm184"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText184"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment183"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment183"&gt;#183&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm183"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText183"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment182"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment182"&gt;#182&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm182"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText182"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment181"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment181"&gt;#181&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm181"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText181"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment186"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment186"&gt;#186&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm186"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText186"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment185"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment185"&gt;#185&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm185"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText185"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment192"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment192"&gt;#192&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm192"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText192"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment191"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment191"&gt;#191&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm191"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText191"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment190"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment190"&gt;#190&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm190"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText190"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment189"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment189"&gt;#189&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm189"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText189"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment188"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment188"&gt;#188&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm188"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText188"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment187"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment187"&gt;#187&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm187"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText187"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="commentMore"&gt;Viewing 15 of 143 comments: &lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;commentcount=all#comments" onclick="return MTComments.GetComments('all');" id="commentViewAll"&gt;view all&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="commentForm"&gt;You must &lt;a href="index.php?title=Special:Userlogin&amp;amp;returntotitle=Blackbook+2+and+3"&gt;login&lt;/a&gt; to post a comment.&lt;/div&gt;&lt;/div&gt;								
				&lt;div class="custom custom5"&gt;
									&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="bodyFooter"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;div class="Wik.is"&gt;&lt;div class="poweredBy"&gt;Powered by &lt;a href=""&gt; Wik.is Express: open source enterprise collaboration and wik software&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;
			&lt;div class="sourceforge" style="text-align: center; margin: 8px 0;"&gt;&lt;a href="http://wik.is/"&gt;&lt;img src="http://wik.is/wp-content/uploads/2015/06/logo1.png" alt=" Wik.is" /&gt;&lt;/a&gt;&lt;/div&gt; 		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;


&lt;script type="text/javascript"&gt;var _endtime = new Date().getTime(); var _size = 40215;&lt;/script&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuTools" style="display:none;"&gt;
	&lt;ul&gt;	&lt;li class="siteListRss"&gt;&lt;a href="Special:ListRss" title="RSS feeds"&gt;&lt;span&gt;&lt;/span&gt;RSS feeds&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteListusers"&gt;&lt;a href="User:" title="Users"&gt;&lt;span&gt;&lt;/span&gt;Users&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteListTemplates"&gt;&lt;a href="Template:" title="Templates"&gt;&lt;span&gt;&lt;/span&gt;Templates&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteSitemap"&gt;&lt;a href="Special:Sitemap" title="Sitemap"&gt;&lt;span&gt;&lt;/span&gt;Sitemap&lt;/a&gt;&lt;/li&gt;
	&lt;li class="sitePopularpages"&gt;&lt;a href="Special:Popularpages" title="Popular pages"&gt;&lt;span&gt;&lt;/span&gt;Popular pages&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteAbout"&gt;&lt;a href="Special:About" title="About"&gt;&lt;span&gt;&lt;/span&gt;About&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;	
&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuPageOptions" style="display:none;"&gt;
	&lt;ul&gt;	&lt;li class="pageEdit disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Edit page"&gt;&lt;span&gt;&lt;/span&gt;Edit page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageAdd disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');" title="New page"&gt;&lt;span&gt;&lt;/span&gt;New page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageRestrict disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Restrict access"&gt;&lt;span&gt;&lt;/span&gt;Restrict access&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageAttach disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Attach file"&gt;&lt;span&gt;&lt;/span&gt;Attach file&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageMove disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Move page"&gt;&lt;span&gt;&lt;/span&gt;Move page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageDelete disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Delete page"&gt;&lt;span&gt;&lt;/span&gt;Delete page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pagePrint "&gt;&lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=print" onclick="menuOff('menuPageOptions');return Print.open('/index.php?title=Blackbook_2_and_3&amp;amp;action=print');" title="Print page"&gt;&lt;span&gt;&lt;/span&gt;Print page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageTags disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Tag"&gt;&lt;span&gt;&lt;/span&gt;Tag&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageEmail disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Email link"&gt;&lt;span&gt;&lt;/span&gt;Email link&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageProperties disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Set page properties"&gt;&lt;span&gt;&lt;/span&gt;Set page properties&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageTalk "&gt;&lt;a href="Talk:Blackbook_2_and_3" onclick="menuOff('menuPageOptions');" title="Talk page"&gt;&lt;span&gt;&lt;/span&gt;Talk page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageWatch "&gt;&lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=watch" onclick="menuOff('menuPageOptions');" title="Watch page"&gt;&lt;span&gt;&lt;/span&gt;Watch page&lt;/a&gt;&lt;/li&gt;
&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuBacklink" style="display:none;"&gt;
	&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuPageContent" style="display:none;"&gt;
	&lt;div class="pageToc"&gt;&lt;h5&gt;Table of contents&lt;/h5&gt;&lt;em&gt;No headers&lt;/em&gt;&lt;/div&gt;&lt;/div&gt;


&lt;div class="ui-msg-wrap" id="MTMessage" style="display: none;"&gt;
	&lt;div class="ui-msg ui-errormsg" id="MTMessageStyle"&gt;
		&lt;div class="ui-msg-opt"&gt;
			&lt;ul&gt;
				&lt;li&gt;&lt;a href="#" class="dismiss" onclick="return MTMessage.Hide();"&gt;dismiss message&lt;/a&gt;&lt;/li&gt;
				&lt;li&gt;&lt;a href="#" class="details" id="MTMessageDetailsLink" onclick="return MTMessage.ShowDetails(this);"&gt;view details&lt;/a&gt;&lt;/li&gt;
			&lt;/ul&gt;
			&lt;div class="ui-msg-autoclose"&gt;
				&lt;span id="MTMessageUnpaused" style="display: inline;"&gt;Message will close by itself in &lt;span id="MTMessageTimer"&gt;&lt;/span&gt; seconds&lt;/span&gt;
				&lt;span id="MTMessagePaused" style="display: none;"&gt;Message timer has been stopped&lt;/span&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		&lt;div class="ui-msg-header" id="MTMessageHeader"&gt;&lt;/div&gt;
		&lt;div class="ui-msg-desc" id="MTMessageDesc"&gt;&lt;/div&gt;
		&lt;div class="ui-msg-desc" id="MTMessageDetails" style="display: none;"&gt;
			&lt;p&gt;Viewing Details:&lt;/p&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;&lt;div id="menuFiller"&gt;&lt;/div&gt;&lt;div id="bodyHeight"&gt;&lt;/div&gt;&lt;script src="urchin.js" type="text/javascript"&gt;&lt;/script&gt;
&lt;!-- Served by ec2-75-101-202-187.compute-1.amazonaws.com in 1.69 secs. --&gt;
&lt;!-- /wik/site/settings: 0.75441813468933--&gt;
&lt;!-- /wik/users/=Anonymous: 0.043669939041138--&gt;
&lt;!-- /wik/site/services/1: 0.0053939819335938--&gt;
&lt;!-- /wik/pages/710/contents: 0.022506952285767--&gt;
&lt;!-- /wik/pages/710: 0.061690092086792--&gt;
&lt;!-- /wik/pages/710/comments: 0.6609480381012--&gt;
&lt;!-- /wik/pages/710/security: 0.019191026687622--&gt;
&lt;!-- /wik/site/nav/=Blackbook%2B2%2Band%2B3/full: 0.051814079284668--&gt;
&lt;!-- Total: 1.6196322441101--&gt;
&lt;!-- Real: 1.6196322441101--&gt;

&lt;/body&gt;
  
&lt;/html&gt;</text>
    <sha1>5b468296ab961ef7a839aa679d29fe37445abcaa</sha1>
  </revision>
  <revision>
    <id>393</id>
    <parentid>392</parentid>
    <timestamp>2016-01-13T16:43:42Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="43556" xml:space="preserve">&lt;nowiki&gt;&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;
 &lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us" dir=""&gt;
 &lt;head&gt;


    &lt;script type="text/javascript"&gt;var _starttime = new Date().getTime();&lt;/script&gt;
    &lt;meta http-equiv="Content-Type" content="text/html; charset=utf-8" /&gt;
    &lt;meta name="robots" content="index,follow" /&gt;
&lt;link rel="shortcut icon" href="favicon.ico" /&gt;
&lt;meta name="generator" content=" Wik.is" /&gt;
&lt;link rel="search" type="application/opensearchdescription+xml" title="Federal Data Web 2.0 Wiki Pilot Search" href="/@gui/opensearch/description" /&gt;    &lt;title&gt;Blackbook 2 and 3 - Federal Data Web 2.0 Wiki Pilot&lt;/title&gt;
    
    &lt;!-- default css --&gt;
    &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/fiesta/_reset.css"/&gt;
    &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/common/css.php" /&gt; &lt;!--[if IE 7]&gt;&lt;style type="text/css"&gt;@import "/skins/common/_ie7.css";&lt;/style&gt;&lt;![endif]--&gt;&lt;!--[if IE 6]&gt;&lt;style type="text/css"&gt;@import "/skins/common/_ie.css";&lt;/style&gt;&lt;![endif]--&gt;    &lt;link rel="stylesheet" type="text/css" media="print" href="skins/common/print.css" /&gt;    
    &lt;!-- default scripting --&gt;
    &lt;script type="text/javascript" src="skins/common/js.php?perms=LOGIN,BROWSE,READ,SUBSCRIBE&amp;amp;lang=en-us"&gt;&lt;/script&gt;    
    &lt;!-- specific screen stylesheets--&gt;
        &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/fiesta/sky-tangerine/css.php"/&gt;
        
    &lt;!-- specific print stylesheets --&gt;
    &lt;link rel="stylesheet" type="text/css" media="print" href="skins/fiesta/print.css" /&gt;
   
    &lt;!-- IE6 &amp; IE7 specific stuff --&gt;
    &lt;!--[if IE]&gt;&lt;meta http-equiv="imagetoolbar" content="no" /&gt;&lt;![endif]--&gt;
    &lt;!--[if IE 6]&gt;&lt;link rel="stylesheet" type="text/css" media="screen" href="/skins/fiesta/sky-tangerine/ie6.php"/&gt;&lt;![endif]--&gt;
    &lt;!--[if IE 7]&gt;&lt;link rel="stylesheet" type="text/css" media="screen" href="/skins/fiesta/sky-tangerine/ie7.php"/&gt;&lt;![endif]--&gt;
    
    	&lt;script type="text/javascript"&gt;

	    _page_redirect = false;
_path_tpl = '/skins/fiesta';
_path_skin = '/skins/fiesta/sky-tangerine';
_path_common = '/skins/common';
_path_icons = '/skins/common/icons';
editToken = 'f50e1eed8f38fedcfc02890ed226112a';
_userName = 'Anonymous';
_userId = '2';
var _editor_styles_path = ['/skins/fiesta/_editor.css', '/skins/fiesta/sky-tangerine/_content.css', ''];
_today = '2 Oct 2010';
baseHref = '/web/20101003032546/http://federaldata.Wik.is';
_page_titlePath = '/';
_page_titleName = 'Blackbook 2 and 3';
_page_ID = 710;
_total_images = 6;
contextTopic = 'Blackbook 2 and 3';
_over_storage_quota = false;
saveFlag = false;

	    
		// remote scripting library
		// (c) copyright 2005 modernmethod, inc
		var sajax_debug_mode = false;
		var sajax_request_type = "POST";

		function sajax_debug(text) {
			if (sajax_debug_mode)
				alert("RSD: " + text);
		};

		function sajax_init_object() {
			sajax_debug("sajax_init_object() called..");

			var A = window.XMLHttpRequest ? new XMLHttpRequest() : window.ActiveXObject ? new ActiveXObject("Microsoft.XMLHTTP") : null;
			if (!A)
				sajax_debug("Could not create connection object.");
			return A;
		};
		function _sajax_do_call(x, func_name, args) {
			var i, x, n;
			var uri;
			var post_data;

			uri = "/index.php";
			if (sajax_request_type == "GET") {
				if (uri.indexOf("?") == -1) 
					uri = uri + "?rs=" + encodeURIComponent(func_name);
				else
					uri = uri + "&amp;rs=" + encodeURIComponent(func_name);
				for (i = 0; i &lt; args.length-1; i++) {
				    var a = args[i];
					uri = uri + "&amp;rsargs[]=" + encodeURIComponent(a);
				}
				uri = uri + "&amp;rsrnd=" + new Date().getTime();
				post_data = null;
			} else {
				post_data = "rs=" + func_name;
				for (i = 0; i &lt; args.length-1; i++) {
				    var a = args[i];
					post_data = post_data + "&amp;rsargs[]=" + encodeURIComponent(a);
				}
			}
			x.open(sajax_request_type, uri, true);
			if (sajax_request_type == "POST") {
				x.setRequestHeader("Method", "POST " + uri + " HTTP/1.1");
				x.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
			}
			x.onreadystatechange = function() {
				if (x.readyState != 4) 
					return;
				if (typeof sajax_debug != 'undefined') sajax_debug("received " + x.responseText);

				var status;
				var data = x.responseText.replace(/^\s+/, '');
				status = data.charAt(0);
				data = data.substring(2);
				if (status == "-") 
					alert("Error: " + data);
				else  
					args[args.length-1](data);
			}
			x.send(post_data);
			sajax_debug(func_name + " uri = " + uri + "/post = " + post_data);
			sajax_debug(func_name + " waiting..");
			return x;
		};
		function sajax_do_call(func_name, args) {
			x = sajax_init_object();
			_sajax_do_call(x, func_name, args);
			delete x;
		};

		function x_breadcrumbSet() { sajax_do_call("breadcrumbSet", x_breadcrumbSet.arguments); };
		function x_wfAdminUserForm() { sajax_do_call("wfAdminUserForm", x_wfAdminUserForm.arguments); };
		function x_wfSetUserOption() { sajax_do_call("wfSetUserOption", x_wfSetUserOption.arguments); };
		function x_wfSetRestrictions() { sajax_do_call("wfSetRestrictions", x_wfSetRestrictions.arguments); };
		function x_setUserOption() { sajax_do_call("setUserOption", x_setUserOption.arguments); };
		function x_wfValidateUserOrGroup() { sajax_do_call("wfValidateUserOrGroup", x_wfValidateUserOrGroup.arguments); };
		function x_wfSaveEdit() { sajax_do_call("wfSaveEdit", x_wfSaveEdit.arguments); };
		function x_wfQueryLinks() { sajax_do_call("wfQueryLinks", x_wfQueryLinks.arguments); };
		function x_loadInplaceEditor() { sajax_do_call("loadInplaceEditor", x_loadInplaceEditor.arguments); };
		function x_doSetbaseHref() { sajax_do_call("doSetbaseHref", x_doSetbaseHref.arguments); };
		function x_showFileAttachments() { sajax_do_call("showFileAttachments", x_showFileAttachments.arguments); };
		function x_doSectionEdit() { sajax_do_call("doSectionEdit", x_doSectionEdit.arguments); };
		function x_postComment() { sajax_do_call("postComment", x_postComment.arguments); };
		function x_getComments() { sajax_do_call("getComments", x_getComments.arguments); };
		function x_deleteComment() { sajax_do_call("deleteComment", x_deleteComment.arguments); };
		function x_editComment() { sajax_do_call("editComment", x_editComment.arguments); };
		function x_wfEmailPage() { sajax_do_call("wfEmailPage", x_wfEmailPage.arguments); };
		function x_wfCheckNewTitle() { sajax_do_call("wfCheckNewTitle", x_wfCheckNewTitle.arguments); };
		function x_wfDeleteFile() { sajax_do_call("wfDeleteFile", x_wfDeleteFile.arguments); };
		function x_wfSetPageProperties() { sajax_do_call("wfSetPageProperties", x_wfSetPageProperties.arguments); };
		function x_wfDeleteTopic() { sajax_do_call("wfDeleteTopic", x_wfDeleteTopic.arguments); };
		function x_wfRenameTopic() { sajax_do_call("wfRenameTopic", x_wfRenameTopic.arguments); };
		function x_wfMoveAttachments() { sajax_do_call("wfMoveAttachments", x_wfMoveAttachments.arguments); };
		function x_wfGetAttachmentUrl() { sajax_do_call("wfGetAttachmentUrl", x_wfGetAttachmentUrl.arguments); };
		function x_wfInlineImageGallery() { sajax_do_call("wfInlineImageGallery", x_wfInlineImageGallery.arguments); };
		function x_wfSetFileDescription() { sajax_do_call("wfSetFileDescription", x_wfSetFileDescription.arguments); };
		function x_wfChangeLoginView() { sajax_do_call("wfChangeLoginView", x_wfChangeLoginView.arguments); };
		function x_wfChangeLoginViewToCreate() { sajax_do_call("wfChangeLoginViewToCreate", x_wfChangeLoginViewToCreate.arguments); };
		function x_wfSaveCredsToSession() { sajax_do_call("wfSaveCredsToSession", x_wfSaveCredsToSession.arguments); };
		function x_wfChangeAddServiceView() { sajax_do_call("wfChangeAddServiceView", x_wfChangeAddServiceView.arguments); };
		function x_wfSaveLoginPageCreds() { sajax_do_call("wfSaveLoginPageCreds", x_wfSaveLoginPageCreds.arguments); };
		function x_wfRemindPassword() { sajax_do_call("wfRemindPassword", x_wfRemindPassword.arguments); };
		function x_wfChangeAvailUsersPage() { sajax_do_call("wfChangeAvailUsersPage", x_wfChangeAvailUsersPage.arguments); };
		
	    window.onbeforeunload = checkForChanges;

	    function checkForChanges() {
	        if (saveFlag &amp;&amp; !doCheckChanges(cur_editor)) {
	        	return "You have made changes to the content without saving your changes. Are you sure you want to exit this page?";
	        }
	    }
	    var aLt = new Array();aLt["attach-no-description"] = 'No description'; aLt["cancel"] = 'Cancel'; aLt["comment-delete"] = 'Are you sure you want to delete this comment?'; aLt["gallery-close"] = 'close'; aLt["gallery-next"] = 'next'; aLt["gallery-prev"] = 'prev'; aLt["internal-error"] = 'Sorry, but there was an internal problem - please try again soon.'; aLt["js-label_cancel"] = 'Cancel'; aLt["js-label_save"] = 'Save'; aLt["js-tooltip_cancel"] = 'Exit Without Saving Changes'; aLt["js-tooltip_save"] = 'Save and Exit (Alt+S)'; aLt["ldap-provide-credentials"] = 'Please provide external service login credentials.'; aLt["loading"] = 'Loading...'; aLt["menu-confirm-delete"] = 'Are you sure you want to delete this file?'; aLt["menu-delete-file"] = 'Delete'; aLt["menu-edit-description"] = 'Edit description'; aLt["menu-move-file"] = 'Move'; aLt["menu-previous-versions"] = 'Previous versions'; aLt["menu-view-original"] = 'View original'; aLt["print-end-notes"] = 'Endnotes'; aLt["ready"] = 'Ready'; aLt["submit"] = 'Submit'; aLt["select-files"] = 'Select files...'; aLt["wikibits-attach-another"] = 'Attach another file'; aLt["wikibits-attach-file"] = 'Attach File'; aLt["wikibits-cant-attach-editing"] = 'Sorry, you can\'t attach files while editing a page. Please close the editor first.'; aLt["wikibits-edit-section"] = 'Edit section'; aLt["wikibits-remove-file"] = 'Remove file';  var wfMsg = function (key) { return aLt[key] ? aLt[key] : 'MISSING: ' + key; };var navMaxWidth = 1600;
	//hook in menu clicking events to the document's body
	YAHOO.util.Event.addListener(document, "click", function () { FileMenu.bodyClick(); DWMenu.BodyClick(); });	
	YAHOO.util.Event.onDOMReady(function () { new clientWindow }); 
	
                
		YAHOO.util.Event.onAvailable("siteNavTree", wik.nav.init, wik.nav, true);
		
	
			YAHOO.util.Event.onDOMReady(function() {
			tb_init('a.lightbox, area.lightbox, input.lightbox, a[@rel=awesomebox]');//pass where to apply thickbox
			imgLoader = new Image();// preload image
			imgLoader.src = tb_pathToImage;
		});
		
		YAHOO.util.Event.onDOMReady(function() { 
			MTComments.HookBehavior();
		});
		&lt;/script&gt;
	
	&lt;!-- styles overwritten via control panel - load this css last --&gt;	
	 
&lt;/head&gt;

&lt;body class="  en-us"&gt;


&lt;noscript&gt;This application requires Javascript to be enabled.&lt;/noscript&gt;

&lt;div class="global"&gt;
	&lt;div class="globalWrap"&gt;
		&lt;div class="header"&gt;
		
			&lt;div class="mastPre"&gt;&lt;/div&gt;
			&lt;div class="mast"&gt;
				
				&lt;div class="siteLogo"&gt;
					&lt;a href="" title="Federal Data Web 2.0 Wiki Pilot"&gt;&lt;img src="skins/fiesta/sky-tangerine/logo.png" alt="Federal Data Web 2.0 Wiki Pilot" title="Federal Data Web 2.0 Wiki Pilot"/&gt;&lt;/a&gt;		
				&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="mastPost"&gt;&lt;/div&gt;
			
			&lt;div class="siteNavPre"&gt;&lt;/div&gt;
			&lt;div class="siteNav"&gt;
				&lt;div class="userAuthPre"&gt;&lt;/div&gt;
							&lt;div class="userAuth"&gt;
			&lt;span&gt;Logged in:&lt;/span&gt;			&lt;span&gt;Logged in as:&lt;/span&gt;					
	 		&lt;a href="index.php?title=Special:Userlogin&amp;amp;returntotitle=Blackbook+2+and+3" class="userLogin"&gt;Log in&lt;/a&gt;		&lt;/div&gt;
						
									&lt;div class="userAuthPost"&gt;&lt;/div&gt;
				
				&lt;div class="custom custom2"&gt;
									&lt;/div&gt;
				
					
				&lt;div class="navPre"&gt;&lt;/div&gt;
					&lt;div id="siteNavTree"&gt;&lt;div class="node dockedNode homeNode lastDocked parentClosed" id="n21" c="n2348,n710,n70,n542,n497,n1144,n702,n2349,n1437,n2346,n990,n35,n33,n34,n526,n543,n1884,n46,n842,n498,n418,n75,n73,n654,n1883,n534,n2368,n704,n661,n653,n711,n1473,n2352,n427,n1140,n2287,n581,n695,n1935,n1134,n500,n2359,n1757" path=""&gt;&lt;a href="" title="Federal Data Web 2.0 Wiki Pilot"&gt;&lt;span&gt;Federal Data Web 2....&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n2348" p="n21" path="Analytics/"&gt;&lt;a href="Analytics" title="Analytics"&gt;&lt;span&gt;Analytics&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling selected" id="n710" p="n21" path="Blackbook_2_and_3/"&gt;&lt;a href="Blackbook_2_and_3" title="Blackbook 2 and 3"&gt;&lt;span&gt;Blackbook 2 and 3&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n70" p="n21" path="Blog_(Web_Log)/"&gt;&lt;a href="Blog_(Web_Log)" title="Blog (Web Log)"&gt;&lt;span&gt;Blog (Web Log)&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n542" p="n21" path="Cambridge_Semantics_Recovery.gov/"&gt;&lt;a href="Cambridge_Semantics_Recovery.gov" title="Cambridge Semantics Recovery.gov"&gt;&lt;span&gt;Cambridge Semantic...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n497" p="n21" path="Comments_and_Innovations_for_the_Open_Government_and_Transparency_Directive/"&gt;&lt;a href="Comments_and_Innovations_for_the_Open_Government_and_Transparency_Directive" title="Comments and Innovations for the Open Government and Transparency Directive"&gt;&lt;span&gt;Comments and Innov...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1144" p="n21" path="Data.gov/"&gt;&lt;a href="Data.gov" title="Data.gov Adds Geoviewer"&gt;&lt;span&gt;Data.gov Adds Geovi...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n702" p="n21" path="Data.gov_Concept_of_Operations_v0.7/"&gt;&lt;a href="Data.gov_Concept_of_Operations_v0.7" title="Data.gov Concept of Operations"&gt;&lt;span&gt;Data.gov Concept of...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n2349" p="n21" path="Data.gov_CONOPS/"&gt;&lt;a href="Data.gov_CONOPS" title="Data.gov CONOPS"&gt;&lt;span&gt;Data.gov CONOPS&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1437" p="n21" path="Data.gov%2fsemantic/"&gt;&lt;a href="Data.gov%2f%2fsemantic" title="Data.gov/semantic"&gt;&lt;span&gt;Data.gov/semantic&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n2346" p="n21" path="Data_Science/" cd="0"&gt;&lt;a href="Data_Science" title="Data Science"&gt;&lt;span&gt;Data Science&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n990" p="n21" path="Executive_Office_of_the_President_-_OMB_and_NSA_Detail/"&gt;&lt;a href="Executive_Office_of_the_President_-_OMB_and_NSA_Detail" title="Executive Office of the President - OMB and NSA Detail for Data.gov"&gt;&lt;span&gt;Executive Office of ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n35" p="n21" path="Federal_Data_Architecture_Subcommittee_(DAS)/" cd="0"&gt;&lt;a href="Federal_Data_Architecture_Subcommittee_(DAS)" title="Federal Data Architecture Subcommittee (DAS)"&gt;&lt;span&gt;Federal Data Archite...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n33" p="n21" path="Federal_Data_Reference_Model/"&gt;&lt;a href="Federal_Data_Reference_Model" title="Federal Data Reference Model"&gt;&lt;span&gt;Federal Data Refere...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n34" p="n21" path="Federal_Data_Reference_Model_2.0/" cd="0"&gt;&lt;a href="Federal_Data_Reference_Model_2.0" title="Federal Data Reference Model 2.0"&gt;&lt;span&gt;Federal Data Refere...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n526" p="n21" path="Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form/" cd="0"&gt;&lt;a href="Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form" title="Federal Enterprise Architecture Reference Model Revision Submission Form (DRM 3.0)"&gt;&lt;span&gt;Federal Enterprise A...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n543" p="n21" path="Federal_Enterprise_Architecture_Security_and_Privacy_Profile_Version_3.0/" cd="0"&gt;&lt;a href="Federal_Enterprise_Architecture_Security_and_Privacy_Profile_Version_3.0" title="Federal Enterprise Architecture Security and Privacy Profile Version 3.0"&gt;&lt;span&gt;Federal Enterprise A...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1884" p="n21" path="Federal_IT_Dashboard/"&gt;&lt;a href="Federal_IT_Dashboard" title="Federal IT Dashboard"&gt;&lt;span&gt;Federal IT Dashboar...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n46" p="n21" path="Federal_Semantic_Interoperability_Community_of_Practice_(SICoP)/" cd="0"&gt;&lt;a href="Federal_Semantic_Interoperability_Community_of_Practice_(SICoP)" title="Federal Semantic Interoperability Community of Practice (SICoP)"&gt;&lt;span&gt;Federal Semantic Int...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n842" p="n21" path="FGDC_Standards_WG_meeting_-_February_23,_2010/"&gt;&lt;a href="FGDC_Standards_WG_meeting_-_February_23%2c_2010" title="FGDC Standards WG Meeting - February 23, 2010"&gt;&lt;span&gt;FGDC Standards WG ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n498" p="n21" path="George_Thomas_on_Recovery.gov/"&gt;&lt;a href="George_Thomas_on_Recovery.gov" title="George Thomas on Recovery.gov"&gt;&lt;span&gt;George Thomas on R...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n418" p="n21" path="Harnessing_the_Power_of_Digital_Data_for_Science_and_Society/" cd="0"&gt;&lt;a href="Harnessing_the_Power_of_Digital_Data_for_Science_and_Society" title="Harnessing the Power of Digital Data for Science and Society"&gt;&lt;span&gt;Harnessing the Powe...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n75" p="n21" path="Interagency_Forum_on_Data_Preservation,_Stewardship,_and_LifeCycle_ESIP_Federation_Meeting,_January_8,_2009/"&gt;&lt;a href="Interagency_Forum_on_Data_Preservation%2c_Stewardship%2c_and_LifeCycle_ESIP_Federation_Meeting%2c_January_8%2c_2009" title="Interagency Forum on Data Preservation, Stewardship, and LifeCycle ESIP Federation Meeting, January 8, 2009"&gt;&lt;span&gt;Interagency Forum o...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n73" p="n21" path="Interagency_Working_Group_on_Digitial_Data/" cd="0"&gt;&lt;a href="Interagency_Working_Group_on_Digitial_Data" title="Interagency Working Group on Digitial Data"&gt;&lt;span&gt;Interagency Working...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n654" p="n21" path="June_4,_2009_How_Does_Government_Become_an_Open_Platform?/"&gt;&lt;a href="June_4%2c_2009_How_Does_Government_Become_an_Open_Platform%3f" title="June 4, 2009 How Does Government Become an Open Platform?"&gt;&lt;span&gt;June 4, 2009 How Do...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1883" p="n21" path="Labor's_Enforcement_Data_Catalog/"&gt;&lt;a href="Labor's_Enforcement_Data_Catalog" title="Labor's Enforcement Data Catalog"&gt;&lt;span&gt;Labor's Enforcement...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling moreNodes" id="n534" p="n21" path="May_13,_2009_Semantic_Web_Meetup/" content="May 13, 2009 Seman..." contentTitle="May 13, 2009 Semantic Web Meetup" hiddenNodes="n2368,n704,n661,n653,n711,n1473,n2352,n427,n1140,n2287,n581,n695,n1935,n1134,n500,n2359,n1757"&gt;&lt;a href="May_13%2c_2009_Semantic_Web_Meetup" title="More..."&gt;&lt;span class="more"&gt;...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2368" p="n21" path="Model_for_Performance-Driven_Government/" cd="0"&gt;&lt;a href="Model_for_Performance-Driven_Government" title="Model for Performance-Driven Government"&gt;&lt;span&gt;Model for Performan...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n704" p="n21" path="NIEM/"&gt;&lt;a href="NIEM" title="NIEM"&gt;&lt;span&gt;NIEM&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n661" p="n21" path="Open_Group_Enterprise_Vocabularly_Workshop_June_3,_2009/"&gt;&lt;a href="Open_Group_Enterprise_Vocabularly_Workshop_June_3%2c_2009" title="Open Group Enterprise Vocabularly Workshop June 3, 2009"&gt;&lt;span&gt;Open Group Enterpri...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n653" p="n21" path="Open_Group_Enterprise_Vocabulary_Workshop_May_20,_2009/"&gt;&lt;a href="Open_Group_Enterprise_Vocabulary_Workshop_May_20%2c_2009" title="Open Group Enterprise Vocabulary Workshop May 20, 2009"&gt;&lt;span&gt;Open Group Enterpri...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n711" p="n21" path="Page_Title/"&gt;&lt;a href="Page_Title" title="Open Government Directive Workshop, January 11, 2010"&gt;&lt;span&gt;Open Government Di...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1473" p="n21" path="Scientific_Data_Management_for_Government_Agencies/"&gt;&lt;a href="Scientific_Data_Management_for_Government_Agencies" title="Scientific Data Management for Government Agencies"&gt;&lt;span&gt;Scientific Data Mana...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2352" p="n21" path="Semantic_eScience/" cd="0"&gt;&lt;a href="Semantic_eScience" title="Semantic eScience"&gt;&lt;span&gt;Semantic eScience&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n427" p="n21" path="Statistical_Abstract_of_the_United_States:_2009/" cd="0"&gt;&lt;a href="Statistical_Abstract_of_the_United_States%3a_2009" title="Statistical Abstract of the United States: 2009"&gt;&lt;span&gt;Statistical Abstract ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n1140" p="n21" path="Statistics/" cd="0"&gt;&lt;a href="Statistics" title="Statistics"&gt;&lt;span&gt;Statistics&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2287" p="n21" path="Survey_of_EPA_and_Other_Federal_Agency_Scientific_Data_Management_Policies_and_Guidance_2010/" cd="0"&gt;&lt;a href="Survey_of_EPA_and_Other_Federal_Agency_Scientific_Data_Management_Policies_and_Guidance_2010" title="Survey of EPA and Other Federal Agency Scientific Data Management Policies and Guidance 2010"&gt;&lt;span&gt;Survey of EPA and O...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n581" p="n21" path="The_Recovery_Dialogue_on_IT_Solutions/" cd="0"&gt;&lt;a href="The_Recovery_Dialogue_on_IT_Solutions" title="The Recovery Dialogue on IT Solutions"&gt;&lt;span&gt;The Recovery Dialog...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n695" p="n21" path="Tools_for_linked_data_from_DERI/"&gt;&lt;a href="Tools_for_linked_data_from_DERI" title="Tools for linked data from DERI"&gt;&lt;span&gt;Tools for linked dat...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1935" p="n21" path="Top_Secret_America/"&gt;&lt;a href="Top_Secret_America" title="Top Secret America"&gt;&lt;span&gt;Top Secret America&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n1134" p="n21" path="Ucore-SL/" cd="0"&gt;&lt;a href="Ucore-SL" title="Ucore-SL"&gt;&lt;span&gt;Ucore-SL&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n500" p="n21" path="W3C_eGovernment_Interest_Group/" cd="0"&gt;&lt;a href="W3C_eGovernment_Interest_Group" title="W3C eGovernment Interest Group"&gt;&lt;span&gt;W3C eGovernment In...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n2359" p="n21" path="Watershed_Boundary_Dataset/"&gt;&lt;a href="Watershed_Boundary_Dataset" title="Watershed Boundary Dataset"&gt;&lt;span&gt;Watershed Boundary ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1757" p="n21" path="White_House_Salaries/"&gt;&lt;a href="White_House_Salaries" title="White House Salaries"&gt;&lt;span&gt;White House Salarie...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;				&lt;div class="navPost"&gt;&lt;/div&gt;
					
				&lt;div class="custom"&gt;
									&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="siteNavPost"&gt;&lt;/div&gt;
		&lt;/div&gt;
				
		&lt;div class="body"&gt;
			&lt;div class="bodyHeader"&gt;
				&lt;div class="pre"&gt;&lt;/div&gt;
				&lt;div class="post"&gt;&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="page"&gt;
				&lt;!-- required print options --&gt;
								
				&lt;div class="custom custom1"&gt;
								&lt;/div&gt;
				
				&lt;div class="siteNav"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
						
	&lt;div class="siteSearch"&gt;
		&lt;fieldset class="search"&gt;
	 		&lt;form action="Special:Search"&gt;
		        &lt;span&gt;Search: &lt;/span&gt;&lt;input id="searchInput" class="inputText" name="search" type="text" value="" /&gt;
				&lt;input type="hidden" name="type" value="fulltext" /&gt;
		        &lt;input type="submit" name="go" class="inputSubmit" value="Find" /&gt;
			&lt;/form&gt;
		&lt;/fieldset&gt;
	&lt;/div&gt;
					
					&lt;ul&gt;
						&lt;li class="userPage"&gt;&lt;a href="User:Anonymous"&gt;&lt;span&gt;&lt;/span&gt;My Page&lt;/a&gt;&lt;/li&gt;
												&lt;li class="siteChanges"&gt;&lt;a href="Special:Recentchanges"&gt;&lt;span&gt;&lt;/span&gt;Recent changes&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteTools"&gt;&lt;a href="#" onclick="return DWMenu.Position('menuTools', this, 0, 0);"&gt;&lt;span&gt;&lt;/span&gt;Tools&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteHelp"&gt;&lt;a href="Resources/Documentation/FAQ/MindTouch_Express"&gt;&lt;span&gt;&lt;/span&gt;Help&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteHelp"&gt;&lt;a href="pro/"&gt;&lt;span&gt;&lt;/span&gt;Go Pro&lt;/a&gt;&lt;/li&gt;					&lt;/ul&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="pageBar"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
					&lt;div class="pageRevision"&gt;
						&lt;!-- last modified --&gt;
						Page last modified &lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=history" title="20:27, 15 Feb 2010"&gt;20:27, 15 Feb 2010&lt;/a&gt; by &lt;a href="User:LucasGraim" class="link-user" rel="internal"&gt;LucasGraim&lt;/a&gt;						&lt;!-- end last modified --&gt;					
					&lt;/div&gt;
					&lt;div class="pageNav"&gt;
						&lt;ul&gt;
							&lt;li class="pageEdit"&gt;&lt;a href="#" title="Edit page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Edit page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageAdd"&gt;&lt;a href="#" title="New page" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;New page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageRestrict"&gt;&lt;a href="#" title="Restrict access" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Restrict access&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageAttach"&gt;&lt;a href="#" title="Attach file" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Attach file&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageMove"&gt;&lt;a href="#" title="Move page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Move page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageDelete"&gt;&lt;a href="#" title="Delete page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Delete page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pagePrint"&gt;&lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=print" title="Print page" onclick="return Print.open('/index.php?title=Blackbook_2_and_3&amp;amp;action=print');" class=""&gt;&lt;span&gt;&lt;/span&gt;Print page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageMore"&gt;&lt;a href="#" onclick="return DWMenu.Position('menuPageOptions', this, 0, 0);"&gt;&lt;span&gt;&lt;/span&gt;More&lt;/a&gt;&lt;/li&gt;
							&lt;li class="navSplit"&gt;&lt;/li&gt;
							&lt;li class="pageToc"&gt;&lt;a href="#" title="Table of contents" onclick="return DWMenu.Position('menuPageContent', this, -2, 0)" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Table of contents&lt;/a&gt;&lt;/li&gt;
						&lt;/ul&gt;
					&lt;/div&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="pageContentFrame"&gt;
				&lt;div class="custom custom4"&gt;
								&lt;/div&gt;
				
				&lt;div id="pageContent" class="pageContent"&gt;
							 				&lt;div class="hierarchy"&gt;
		 					&lt;span class="dw-hierarchy"&gt;&lt;a href=""&gt;Federal Data Web 2.0 Wiki Pilot&lt;/a&gt; &amp;gt; Blackbook 2 and 3&lt;/span&gt;		 				&lt;/div&gt;
	 								
										&lt;div class="pageTitle"&gt;
												&lt;h1 id="title"&gt;&lt;span  class="pageRestricted" &gt;Blackbook 2 and 3&lt;/span&gt;&lt;/h1&gt;
					&lt;/div&gt;
					
								
					&lt;div class="pageStatus"&gt;
 					     					&lt;/div&gt;
 					
 							
					&lt;div class="PageDW-Blackbook2and3"&gt;								
	 				&lt;div id="page-top"&gt;&lt;div id="pageToc"&gt;&lt;div class="pageToc"&gt;&lt;h5&gt;Table of contents&lt;/h5&gt;&lt;em&gt;No headers&lt;/em&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="pageText" id="pageText"&gt; &lt;p&gt;NSA&amp;rsquo;s Blackbook 2 and 3 - The Standard in Semantic Web Technology for Data Management:&lt;/p&gt; &lt;p&gt;Blackbook2 is a project architected by Intervise&amp;rsquo;s Chief Technology Officer (Scott Streit), which moved into open source on September 1, 2009. Blackbook2 is a standard for semantic web processing and is currently used, in production or pilots, at the Department of Defense, Dole Foods, and the Environmental Protection Agency, just to name a few. Without changing Blackbook2, merely adding new data, Blackbook2 processes anything from Shipping Visibility Data to classified, analytical processing.&lt;/p&gt; &lt;p&gt;For &lt;a class=" external" rel="external nofollow" target="_blank" href="" title="http://www.resumesplanet.com"&gt; resume writers&lt;/a&gt;, web application framework for data analysis, Blackbook2's architecture provides secure support for visualization, transformation, data source integration, asynchronous operations, and is vocabulary agnostic. Application programming interfaces (APIs) exist for plugin components that visualize, discover, transform, extract, enrich, or filter graph&amp;#8208;based data such as social networks. Data sources of many types (RDBMs, Documents, RSS) can be mapped into Blackbook2 as RDF/OWL, either by Ingest or real-time mapping solutions such as D2RQ.&lt;/p&gt; &lt;p&gt;The Blackbook2 architecture provides asynchronous operations via a message bus backend so that results are provided just-in-time to real&amp;#8208;time users or to workflows that may run for hours. Blackbook2 is vocabulary agnostic: it can provide mapping to a common ontology for all data sources or it can accommodate disparate vocabularies with common vocabulary subsets (e.g., Dublin Core, VCard). Finally, Blackbook2 is accredited for multi-level security via role-based access and provides integrated logging via standard interfaces (JAAS and Log4J).&lt;/p&gt; &lt;p&gt;Blackbook 2, and now 3, is available free to Federal government employees and is currently running on the NSA CloudBase Cloud Computing Platform. Software, documentation, and collaboration are available at &lt;a class="external" rel="external nofollow" target="_blank" href="wiki/index.php/Main_Page" title="http://rabasrv.jhuapl.edu/wiki/index.php/Main_Page"&gt;http://rabasrv.jhuapl.edu/wiki/index.php/Main_Page&lt;/a&gt;&amp;nbsp; by contacting Buster Fields at &lt;a class="link-mailto" rel="external nofollow" target="_blank" href="mailto:hlfield@nsa.gov" title="mailto:hlfield@nsa.gov"&gt;hlfield@nsa.gov&lt;/a&gt; .&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="printfooter" id="printfooter"&gt;&lt;hr /&gt;
&lt;p&gt;Retrieved from "&lt;a href="Blackbook_2_and_3"&gt;http://federaldata.Wik.is/Blackbook_2_and_3&lt;/a&gt;"&lt;/p&gt;
&lt;/div&gt;
	 				&lt;/div&gt;
				&lt;/div&gt;
				&lt;/div&gt;
				&lt;div class="DW-clear"&gt;&lt;/div&gt;
								&lt;div class="pageInfo"&gt;
					&lt;dl&gt;
						&lt;dt class="pageTags"&gt;&lt;span&gt;&lt;/span&gt;Tag page&lt;/dt&gt;
						&lt;dd class="pageTags"&gt;
			 				&lt;div id="pageTags"&gt;&lt;div class="pageTagList"&gt;&lt;div class="item taglist"&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;		 				&lt;/dd&gt;
						
						&lt;dt class="pageIncomingLinks"&gt;&lt;span&gt;&lt;/span&gt;What links here&lt;/dt&gt;
						&lt;dd class="pageIncomingLinks"&gt;&lt;/dd&gt;
					&lt;/dl&gt;
				&lt;/div&gt;
				
								
				&lt;div class="file"&gt;
					&lt;h2&gt;Files 0&lt;/h2&gt;
					&lt;div class="fileAdd"&gt;
						&lt;a href="Blackbook_2_and_3" class="disabled" onclick="return false"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="attach" alt="" /&gt;&lt;/span&gt;&lt;span class="text"&gt;Attach file or image&lt;/span&gt;&lt;/a&gt;					&lt;/div&gt;
					&lt;div class="fileList"&gt;
		 				&lt;div id="pageFiles"&gt;&lt;div class="nofiles"&gt;&amp;nbsp;&lt;/div&gt;&lt;/div&gt;					&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="gallery"&gt;
					&lt;h2&gt;Images 0&lt;/h2&gt;
	 				&lt;div id="pageGalleryWrap"&gt;&lt;div class="nofiles"&gt;&amp;nbsp;&lt;/div&gt;&lt;/div&gt;				&lt;/div&gt;
				
 				&lt;div id="comments"&gt;&lt;div class="comments"&gt;&lt;div class="commentMore"&gt;Viewing 15 of 143 comments: &lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;commentcount=all#comments" onclick="return MTComments.GetComments('all');" id="commentViewAll"&gt;view all&lt;/a&gt;&lt;/div&gt;&lt;div class="comment" id="comment179"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment179"&gt;#179&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm179"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText179"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment177"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment177"&gt;#177&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm177"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText177"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment176"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment176"&gt;#176&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm176"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText176"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment184"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment184"&gt;#184&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm184"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText184"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment183"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment183"&gt;#183&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm183"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText183"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment182"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment182"&gt;#182&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm182"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText182"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment181"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment181"&gt;#181&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm181"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText181"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment186"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment186"&gt;#186&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm186"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText186"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment185"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment185"&gt;#185&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm185"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText185"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment192"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment192"&gt;#192&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm192"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText192"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment191"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment191"&gt;#191&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm191"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText191"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment190"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment190"&gt;#190&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm190"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText190"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment189"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment189"&gt;#189&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm189"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText189"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment188"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment188"&gt;#188&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm188"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText188"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment187"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment187"&gt;#187&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm187"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText187"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="commentMore"&gt;Viewing 15 of 143 comments: &lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;commentcount=all#comments" onclick="return MTComments.GetComments('all');" id="commentViewAll"&gt;view all&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="commentForm"&gt;You must &lt;a href="index.php?title=Special:Userlogin&amp;amp;returntotitle=Blackbook+2+and+3"&gt;login&lt;/a&gt; to post a comment.&lt;/div&gt;&lt;/div&gt;								
				&lt;div class="custom custom5"&gt;
									&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="bodyFooter"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;div class="Wik.is"&gt;&lt;div class="poweredBy"&gt;Powered by &lt;a href=""&gt; Wik.is Express: open source enterprise collaboration and wik software&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;
			&lt;div class="sourceforge" style="text-align: center; margin: 8px 0;"&gt;&lt;a href="http://wik.is/"&gt;&lt;img src="http://wik.is/wp-content/uploads/2015/06/logo1.png" alt=" Wik.is" /&gt;&lt;/a&gt;&lt;/div&gt; 		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;


&lt;script type="text/javascript"&gt;var _endtime = new Date().getTime(); var _size = 40215;&lt;/script&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuTools" style="display:none;"&gt;
	&lt;ul&gt;	&lt;li class="siteListRss"&gt;&lt;a href="Special:ListRss" title="RSS feeds"&gt;&lt;span&gt;&lt;/span&gt;RSS feeds&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteListusers"&gt;&lt;a href="User:" title="Users"&gt;&lt;span&gt;&lt;/span&gt;Users&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteListTemplates"&gt;&lt;a href="Template:" title="Templates"&gt;&lt;span&gt;&lt;/span&gt;Templates&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteSitemap"&gt;&lt;a href="Special:Sitemap" title="Sitemap"&gt;&lt;span&gt;&lt;/span&gt;Sitemap&lt;/a&gt;&lt;/li&gt;
	&lt;li class="sitePopularpages"&gt;&lt;a href="Special:Popularpages" title="Popular pages"&gt;&lt;span&gt;&lt;/span&gt;Popular pages&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteAbout"&gt;&lt;a href="Special:About" title="About"&gt;&lt;span&gt;&lt;/span&gt;About&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;	
&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuPageOptions" style="display:none;"&gt;
	&lt;ul&gt;	&lt;li class="pageEdit disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Edit page"&gt;&lt;span&gt;&lt;/span&gt;Edit page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageAdd disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');" title="New page"&gt;&lt;span&gt;&lt;/span&gt;New page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageRestrict disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Restrict access"&gt;&lt;span&gt;&lt;/span&gt;Restrict access&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageAttach disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Attach file"&gt;&lt;span&gt;&lt;/span&gt;Attach file&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageMove disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Move page"&gt;&lt;span&gt;&lt;/span&gt;Move page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageDelete disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Delete page"&gt;&lt;span&gt;&lt;/span&gt;Delete page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pagePrint "&gt;&lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=print" onclick="menuOff('menuPageOptions');return Print.open('/index.php?title=Blackbook_2_and_3&amp;amp;action=print');" title="Print page"&gt;&lt;span&gt;&lt;/span&gt;Print page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageTags disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Tag"&gt;&lt;span&gt;&lt;/span&gt;Tag&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageEmail disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Email link"&gt;&lt;span&gt;&lt;/span&gt;Email link&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageProperties disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Set page properties"&gt;&lt;span&gt;&lt;/span&gt;Set page properties&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageTalk "&gt;&lt;a href="Talk:Blackbook_2_and_3" onclick="menuOff('menuPageOptions');" title="Talk page"&gt;&lt;span&gt;&lt;/span&gt;Talk page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageWatch "&gt;&lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=watch" onclick="menuOff('menuPageOptions');" title="Watch page"&gt;&lt;span&gt;&lt;/span&gt;Watch page&lt;/a&gt;&lt;/li&gt;
&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuBacklink" style="display:none;"&gt;
	&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuPageContent" style="display:none;"&gt;
	&lt;div class="pageToc"&gt;&lt;h5&gt;Table of contents&lt;/h5&gt;&lt;em&gt;No headers&lt;/em&gt;&lt;/div&gt;&lt;/div&gt;


&lt;div class="ui-msg-wrap" id="MTMessage" style="display: none;"&gt;
	&lt;div class="ui-msg ui-errormsg" id="MTMessageStyle"&gt;
		&lt;div class="ui-msg-opt"&gt;
			&lt;ul&gt;
				&lt;li&gt;&lt;a href="#" class="dismiss" onclick="return MTMessage.Hide();"&gt;dismiss message&lt;/a&gt;&lt;/li&gt;
				&lt;li&gt;&lt;a href="#" class="details" id="MTMessageDetailsLink" onclick="return MTMessage.ShowDetails(this);"&gt;view details&lt;/a&gt;&lt;/li&gt;
			&lt;/ul&gt;
			&lt;div class="ui-msg-autoclose"&gt;
				&lt;span id="MTMessageUnpaused" style="display: inline;"&gt;Message will close by itself in &lt;span id="MTMessageTimer"&gt;&lt;/span&gt; seconds&lt;/span&gt;
				&lt;span id="MTMessagePaused" style="display: none;"&gt;Message timer has been stopped&lt;/span&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		&lt;div class="ui-msg-header" id="MTMessageHeader"&gt;&lt;/div&gt;
		&lt;div class="ui-msg-desc" id="MTMessageDesc"&gt;&lt;/div&gt;
		&lt;div class="ui-msg-desc" id="MTMessageDetails" style="display: none;"&gt;
			&lt;p&gt;Viewing Details:&lt;/p&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;&lt;div id="menuFiller"&gt;&lt;/div&gt;&lt;div id="bodyHeight"&gt;&lt;/div&gt;&lt;script src="urchin.js" type="text/javascript"&gt;&lt;/script&gt;
&lt;!-- Served by ec2-75-101-202-187.compute-1.amazonaws.com in 1.69 secs. --&gt;
&lt;!-- /wik/site/settings: 0.75441813468933--&gt;
&lt;!-- /wik/users/=Anonymous: 0.043669939041138--&gt;
&lt;!-- /wik/site/services/1: 0.0053939819335938--&gt;
&lt;!-- /wik/pages/710/contents: 0.022506952285767--&gt;
&lt;!-- /wik/pages/710: 0.061690092086792--&gt;
&lt;!-- /wik/pages/710/comments: 0.6609480381012--&gt;
&lt;!-- /wik/pages/710/security: 0.019191026687622--&gt;
&lt;!-- /wik/site/nav/=Blackbook%2B2%2Band%2B3/full: 0.051814079284668--&gt;
&lt;!-- Total: 1.6196322441101--&gt;
&lt;!-- Real: 1.6196322441101--&gt;

&lt;/body&gt;
  
&lt;/html&gt;
&lt;/nowiki&gt;</text>
    <sha1>1375eeee39624fec67e64330fe14e3f44a0a64da</sha1>
  </revision>
  <revision>
    <id>394</id>
    <parentid>393</parentid>
    <timestamp>2016-01-13T16:44:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Undo revision 393 by [[Special:Contributions/Eddie|Eddie]] ([[User talk:Eddie|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="43538" xml:space="preserve">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;
 &lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us" dir=""&gt;
 &lt;head&gt;


    &lt;script type="text/javascript"&gt;var _starttime = new Date().getTime();&lt;/script&gt;
    &lt;meta http-equiv="Content-Type" content="text/html; charset=utf-8" /&gt;
    &lt;meta name="robots" content="index,follow" /&gt;
&lt;link rel="shortcut icon" href="favicon.ico" /&gt;
&lt;meta name="generator" content=" Wik.is" /&gt;
&lt;link rel="search" type="application/opensearchdescription+xml" title="Federal Data Web 2.0 Wiki Pilot Search" href="/@gui/opensearch/description" /&gt;    &lt;title&gt;Blackbook 2 and 3 - Federal Data Web 2.0 Wiki Pilot&lt;/title&gt;
    
    &lt;!-- default css --&gt;
    &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/fiesta/_reset.css"/&gt;
    &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/common/css.php" /&gt; &lt;!--[if IE 7]&gt;&lt;style type="text/css"&gt;@import "/skins/common/_ie7.css";&lt;/style&gt;&lt;![endif]--&gt;&lt;!--[if IE 6]&gt;&lt;style type="text/css"&gt;@import "/skins/common/_ie.css";&lt;/style&gt;&lt;![endif]--&gt;    &lt;link rel="stylesheet" type="text/css" media="print" href="skins/common/print.css" /&gt;    
    &lt;!-- default scripting --&gt;
    &lt;script type="text/javascript" src="skins/common/js.php?perms=LOGIN,BROWSE,READ,SUBSCRIBE&amp;amp;lang=en-us"&gt;&lt;/script&gt;    
    &lt;!-- specific screen stylesheets--&gt;
        &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/fiesta/sky-tangerine/css.php"/&gt;
        
    &lt;!-- specific print stylesheets --&gt;
    &lt;link rel="stylesheet" type="text/css" media="print" href="skins/fiesta/print.css" /&gt;
   
    &lt;!-- IE6 &amp; IE7 specific stuff --&gt;
    &lt;!--[if IE]&gt;&lt;meta http-equiv="imagetoolbar" content="no" /&gt;&lt;![endif]--&gt;
    &lt;!--[if IE 6]&gt;&lt;link rel="stylesheet" type="text/css" media="screen" href="/skins/fiesta/sky-tangerine/ie6.php"/&gt;&lt;![endif]--&gt;
    &lt;!--[if IE 7]&gt;&lt;link rel="stylesheet" type="text/css" media="screen" href="/skins/fiesta/sky-tangerine/ie7.php"/&gt;&lt;![endif]--&gt;
    
    	&lt;script type="text/javascript"&gt;

	    _page_redirect = false;
_path_tpl = '/skins/fiesta';
_path_skin = '/skins/fiesta/sky-tangerine';
_path_common = '/skins/common';
_path_icons = '/skins/common/icons';
editToken = 'f50e1eed8f38fedcfc02890ed226112a';
_userName = 'Anonymous';
_userId = '2';
var _editor_styles_path = ['/skins/fiesta/_editor.css', '/skins/fiesta/sky-tangerine/_content.css', ''];
_today = '2 Oct 2010';
baseHref = '/web/20101003032546/http://federaldata.Wik.is';
_page_titlePath = '/';
_page_titleName = 'Blackbook 2 and 3';
_page_ID = 710;
_total_images = 6;
contextTopic = 'Blackbook 2 and 3';
_over_storage_quota = false;
saveFlag = false;

	    
		// remote scripting library
		// (c) copyright 2005 modernmethod, inc
		var sajax_debug_mode = false;
		var sajax_request_type = "POST";

		function sajax_debug(text) {
			if (sajax_debug_mode)
				alert("RSD: " + text);
		};

		function sajax_init_object() {
			sajax_debug("sajax_init_object() called..");

			var A = window.XMLHttpRequest ? new XMLHttpRequest() : window.ActiveXObject ? new ActiveXObject("Microsoft.XMLHTTP") : null;
			if (!A)
				sajax_debug("Could not create connection object.");
			return A;
		};
		function _sajax_do_call(x, func_name, args) {
			var i, x, n;
			var uri;
			var post_data;

			uri = "/index.php";
			if (sajax_request_type == "GET") {
				if (uri.indexOf("?") == -1) 
					uri = uri + "?rs=" + encodeURIComponent(func_name);
				else
					uri = uri + "&amp;rs=" + encodeURIComponent(func_name);
				for (i = 0; i &lt; args.length-1; i++) {
				    var a = args[i];
					uri = uri + "&amp;rsargs[]=" + encodeURIComponent(a);
				}
				uri = uri + "&amp;rsrnd=" + new Date().getTime();
				post_data = null;
			} else {
				post_data = "rs=" + func_name;
				for (i = 0; i &lt; args.length-1; i++) {
				    var a = args[i];
					post_data = post_data + "&amp;rsargs[]=" + encodeURIComponent(a);
				}
			}
			x.open(sajax_request_type, uri, true);
			if (sajax_request_type == "POST") {
				x.setRequestHeader("Method", "POST " + uri + " HTTP/1.1");
				x.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
			}
			x.onreadystatechange = function() {
				if (x.readyState != 4) 
					return;
				if (typeof sajax_debug != 'undefined') sajax_debug("received " + x.responseText);

				var status;
				var data = x.responseText.replace(/^\s+/, '');
				status = data.charAt(0);
				data = data.substring(2);
				if (status == "-") 
					alert("Error: " + data);
				else  
					args[args.length-1](data);
			}
			x.send(post_data);
			sajax_debug(func_name + " uri = " + uri + "/post = " + post_data);
			sajax_debug(func_name + " waiting..");
			return x;
		};
		function sajax_do_call(func_name, args) {
			x = sajax_init_object();
			_sajax_do_call(x, func_name, args);
			delete x;
		};

		function x_breadcrumbSet() { sajax_do_call("breadcrumbSet", x_breadcrumbSet.arguments); };
		function x_wfAdminUserForm() { sajax_do_call("wfAdminUserForm", x_wfAdminUserForm.arguments); };
		function x_wfSetUserOption() { sajax_do_call("wfSetUserOption", x_wfSetUserOption.arguments); };
		function x_wfSetRestrictions() { sajax_do_call("wfSetRestrictions", x_wfSetRestrictions.arguments); };
		function x_setUserOption() { sajax_do_call("setUserOption", x_setUserOption.arguments); };
		function x_wfValidateUserOrGroup() { sajax_do_call("wfValidateUserOrGroup", x_wfValidateUserOrGroup.arguments); };
		function x_wfSaveEdit() { sajax_do_call("wfSaveEdit", x_wfSaveEdit.arguments); };
		function x_wfQueryLinks() { sajax_do_call("wfQueryLinks", x_wfQueryLinks.arguments); };
		function x_loadInplaceEditor() { sajax_do_call("loadInplaceEditor", x_loadInplaceEditor.arguments); };
		function x_doSetbaseHref() { sajax_do_call("doSetbaseHref", x_doSetbaseHref.arguments); };
		function x_showFileAttachments() { sajax_do_call("showFileAttachments", x_showFileAttachments.arguments); };
		function x_doSectionEdit() { sajax_do_call("doSectionEdit", x_doSectionEdit.arguments); };
		function x_postComment() { sajax_do_call("postComment", x_postComment.arguments); };
		function x_getComments() { sajax_do_call("getComments", x_getComments.arguments); };
		function x_deleteComment() { sajax_do_call("deleteComment", x_deleteComment.arguments); };
		function x_editComment() { sajax_do_call("editComment", x_editComment.arguments); };
		function x_wfEmailPage() { sajax_do_call("wfEmailPage", x_wfEmailPage.arguments); };
		function x_wfCheckNewTitle() { sajax_do_call("wfCheckNewTitle", x_wfCheckNewTitle.arguments); };
		function x_wfDeleteFile() { sajax_do_call("wfDeleteFile", x_wfDeleteFile.arguments); };
		function x_wfSetPageProperties() { sajax_do_call("wfSetPageProperties", x_wfSetPageProperties.arguments); };
		function x_wfDeleteTopic() { sajax_do_call("wfDeleteTopic", x_wfDeleteTopic.arguments); };
		function x_wfRenameTopic() { sajax_do_call("wfRenameTopic", x_wfRenameTopic.arguments); };
		function x_wfMoveAttachments() { sajax_do_call("wfMoveAttachments", x_wfMoveAttachments.arguments); };
		function x_wfGetAttachmentUrl() { sajax_do_call("wfGetAttachmentUrl", x_wfGetAttachmentUrl.arguments); };
		function x_wfInlineImageGallery() { sajax_do_call("wfInlineImageGallery", x_wfInlineImageGallery.arguments); };
		function x_wfSetFileDescription() { sajax_do_call("wfSetFileDescription", x_wfSetFileDescription.arguments); };
		function x_wfChangeLoginView() { sajax_do_call("wfChangeLoginView", x_wfChangeLoginView.arguments); };
		function x_wfChangeLoginViewToCreate() { sajax_do_call("wfChangeLoginViewToCreate", x_wfChangeLoginViewToCreate.arguments); };
		function x_wfSaveCredsToSession() { sajax_do_call("wfSaveCredsToSession", x_wfSaveCredsToSession.arguments); };
		function x_wfChangeAddServiceView() { sajax_do_call("wfChangeAddServiceView", x_wfChangeAddServiceView.arguments); };
		function x_wfSaveLoginPageCreds() { sajax_do_call("wfSaveLoginPageCreds", x_wfSaveLoginPageCreds.arguments); };
		function x_wfRemindPassword() { sajax_do_call("wfRemindPassword", x_wfRemindPassword.arguments); };
		function x_wfChangeAvailUsersPage() { sajax_do_call("wfChangeAvailUsersPage", x_wfChangeAvailUsersPage.arguments); };
		
	    window.onbeforeunload = checkForChanges;

	    function checkForChanges() {
	        if (saveFlag &amp;&amp; !doCheckChanges(cur_editor)) {
	        	return "You have made changes to the content without saving your changes. Are you sure you want to exit this page?";
	        }
	    }
	    var aLt = new Array();aLt["attach-no-description"] = 'No description'; aLt["cancel"] = 'Cancel'; aLt["comment-delete"] = 'Are you sure you want to delete this comment?'; aLt["gallery-close"] = 'close'; aLt["gallery-next"] = 'next'; aLt["gallery-prev"] = 'prev'; aLt["internal-error"] = 'Sorry, but there was an internal problem - please try again soon.'; aLt["js-label_cancel"] = 'Cancel'; aLt["js-label_save"] = 'Save'; aLt["js-tooltip_cancel"] = 'Exit Without Saving Changes'; aLt["js-tooltip_save"] = 'Save and Exit (Alt+S)'; aLt["ldap-provide-credentials"] = 'Please provide external service login credentials.'; aLt["loading"] = 'Loading...'; aLt["menu-confirm-delete"] = 'Are you sure you want to delete this file?'; aLt["menu-delete-file"] = 'Delete'; aLt["menu-edit-description"] = 'Edit description'; aLt["menu-move-file"] = 'Move'; aLt["menu-previous-versions"] = 'Previous versions'; aLt["menu-view-original"] = 'View original'; aLt["print-end-notes"] = 'Endnotes'; aLt["ready"] = 'Ready'; aLt["submit"] = 'Submit'; aLt["select-files"] = 'Select files...'; aLt["wikibits-attach-another"] = 'Attach another file'; aLt["wikibits-attach-file"] = 'Attach File'; aLt["wikibits-cant-attach-editing"] = 'Sorry, you can\'t attach files while editing a page. Please close the editor first.'; aLt["wikibits-edit-section"] = 'Edit section'; aLt["wikibits-remove-file"] = 'Remove file';  var wfMsg = function (key) { return aLt[key] ? aLt[key] : 'MISSING: ' + key; };var navMaxWidth = 1600;
	//hook in menu clicking events to the document's body
	YAHOO.util.Event.addListener(document, "click", function () { FileMenu.bodyClick(); DWMenu.BodyClick(); });	
	YAHOO.util.Event.onDOMReady(function () { new clientWindow }); 
	
                
		YAHOO.util.Event.onAvailable("siteNavTree", wik.nav.init, wik.nav, true);
		
	
			YAHOO.util.Event.onDOMReady(function() {
			tb_init('a.lightbox, area.lightbox, input.lightbox, a[@rel=awesomebox]');//pass where to apply thickbox
			imgLoader = new Image();// preload image
			imgLoader.src = tb_pathToImage;
		});
		
		YAHOO.util.Event.onDOMReady(function() { 
			MTComments.HookBehavior();
		});
		&lt;/script&gt;
	
	&lt;!-- styles overwritten via control panel - load this css last --&gt;	
	 
&lt;/head&gt;

&lt;body class="  en-us"&gt;


&lt;noscript&gt;This application requires Javascript to be enabled.&lt;/noscript&gt;

&lt;div class="global"&gt;
	&lt;div class="globalWrap"&gt;
		&lt;div class="header"&gt;
		
			&lt;div class="mastPre"&gt;&lt;/div&gt;
			&lt;div class="mast"&gt;
				
				&lt;div class="siteLogo"&gt;
					&lt;a href="" title="Federal Data Web 2.0 Wiki Pilot"&gt;&lt;img src="skins/fiesta/sky-tangerine/logo.png" alt="Federal Data Web 2.0 Wiki Pilot" title="Federal Data Web 2.0 Wiki Pilot"/&gt;&lt;/a&gt;		
				&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="mastPost"&gt;&lt;/div&gt;
			
			&lt;div class="siteNavPre"&gt;&lt;/div&gt;
			&lt;div class="siteNav"&gt;
				&lt;div class="userAuthPre"&gt;&lt;/div&gt;
							&lt;div class="userAuth"&gt;
			&lt;span&gt;Logged in:&lt;/span&gt;			&lt;span&gt;Logged in as:&lt;/span&gt;					
	 		&lt;a href="index.php?title=Special:Userlogin&amp;amp;returntotitle=Blackbook+2+and+3" class="userLogin"&gt;Log in&lt;/a&gt;		&lt;/div&gt;
						
									&lt;div class="userAuthPost"&gt;&lt;/div&gt;
				
				&lt;div class="custom custom2"&gt;
									&lt;/div&gt;
				
					
				&lt;div class="navPre"&gt;&lt;/div&gt;
					&lt;div id="siteNavTree"&gt;&lt;div class="node dockedNode homeNode lastDocked parentClosed" id="n21" c="n2348,n710,n70,n542,n497,n1144,n702,n2349,n1437,n2346,n990,n35,n33,n34,n526,n543,n1884,n46,n842,n498,n418,n75,n73,n654,n1883,n534,n2368,n704,n661,n653,n711,n1473,n2352,n427,n1140,n2287,n581,n695,n1935,n1134,n500,n2359,n1757" path=""&gt;&lt;a href="" title="Federal Data Web 2.0 Wiki Pilot"&gt;&lt;span&gt;Federal Data Web 2....&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n2348" p="n21" path="Analytics/"&gt;&lt;a href="Analytics" title="Analytics"&gt;&lt;span&gt;Analytics&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling selected" id="n710" p="n21" path="Blackbook_2_and_3/"&gt;&lt;a href="Blackbook_2_and_3" title="Blackbook 2 and 3"&gt;&lt;span&gt;Blackbook 2 and 3&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n70" p="n21" path="Blog_(Web_Log)/"&gt;&lt;a href="Blog_(Web_Log)" title="Blog (Web Log)"&gt;&lt;span&gt;Blog (Web Log)&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n542" p="n21" path="Cambridge_Semantics_Recovery.gov/"&gt;&lt;a href="Cambridge_Semantics_Recovery.gov" title="Cambridge Semantics Recovery.gov"&gt;&lt;span&gt;Cambridge Semantic...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n497" p="n21" path="Comments_and_Innovations_for_the_Open_Government_and_Transparency_Directive/"&gt;&lt;a href="Comments_and_Innovations_for_the_Open_Government_and_Transparency_Directive" title="Comments and Innovations for the Open Government and Transparency Directive"&gt;&lt;span&gt;Comments and Innov...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1144" p="n21" path="Data.gov/"&gt;&lt;a href="Data.gov" title="Data.gov Adds Geoviewer"&gt;&lt;span&gt;Data.gov Adds Geovi...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n702" p="n21" path="Data.gov_Concept_of_Operations_v0.7/"&gt;&lt;a href="Data.gov_Concept_of_Operations_v0.7" title="Data.gov Concept of Operations"&gt;&lt;span&gt;Data.gov Concept of...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n2349" p="n21" path="Data.gov_CONOPS/"&gt;&lt;a href="Data.gov_CONOPS" title="Data.gov CONOPS"&gt;&lt;span&gt;Data.gov CONOPS&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1437" p="n21" path="Data.gov%2fsemantic/"&gt;&lt;a href="Data.gov%2f%2fsemantic" title="Data.gov/semantic"&gt;&lt;span&gt;Data.gov/semantic&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n2346" p="n21" path="Data_Science/" cd="0"&gt;&lt;a href="Data_Science" title="Data Science"&gt;&lt;span&gt;Data Science&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n990" p="n21" path="Executive_Office_of_the_President_-_OMB_and_NSA_Detail/"&gt;&lt;a href="Executive_Office_of_the_President_-_OMB_and_NSA_Detail" title="Executive Office of the President - OMB and NSA Detail for Data.gov"&gt;&lt;span&gt;Executive Office of ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n35" p="n21" path="Federal_Data_Architecture_Subcommittee_(DAS)/" cd="0"&gt;&lt;a href="Federal_Data_Architecture_Subcommittee_(DAS)" title="Federal Data Architecture Subcommittee (DAS)"&gt;&lt;span&gt;Federal Data Archite...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n33" p="n21" path="Federal_Data_Reference_Model/"&gt;&lt;a href="Federal_Data_Reference_Model" title="Federal Data Reference Model"&gt;&lt;span&gt;Federal Data Refere...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n34" p="n21" path="Federal_Data_Reference_Model_2.0/" cd="0"&gt;&lt;a href="Federal_Data_Reference_Model_2.0" title="Federal Data Reference Model 2.0"&gt;&lt;span&gt;Federal Data Refere...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n526" p="n21" path="Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form/" cd="0"&gt;&lt;a href="Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form" title="Federal Enterprise Architecture Reference Model Revision Submission Form (DRM 3.0)"&gt;&lt;span&gt;Federal Enterprise A...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n543" p="n21" path="Federal_Enterprise_Architecture_Security_and_Privacy_Profile_Version_3.0/" cd="0"&gt;&lt;a href="Federal_Enterprise_Architecture_Security_and_Privacy_Profile_Version_3.0" title="Federal Enterprise Architecture Security and Privacy Profile Version 3.0"&gt;&lt;span&gt;Federal Enterprise A...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1884" p="n21" path="Federal_IT_Dashboard/"&gt;&lt;a href="Federal_IT_Dashboard" title="Federal IT Dashboard"&gt;&lt;span&gt;Federal IT Dashboar...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n46" p="n21" path="Federal_Semantic_Interoperability_Community_of_Practice_(SICoP)/" cd="0"&gt;&lt;a href="Federal_Semantic_Interoperability_Community_of_Practice_(SICoP)" title="Federal Semantic Interoperability Community of Practice (SICoP)"&gt;&lt;span&gt;Federal Semantic Int...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n842" p="n21" path="FGDC_Standards_WG_meeting_-_February_23,_2010/"&gt;&lt;a href="FGDC_Standards_WG_meeting_-_February_23%2c_2010" title="FGDC Standards WG Meeting - February 23, 2010"&gt;&lt;span&gt;FGDC Standards WG ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n498" p="n21" path="George_Thomas_on_Recovery.gov/"&gt;&lt;a href="George_Thomas_on_Recovery.gov" title="George Thomas on Recovery.gov"&gt;&lt;span&gt;George Thomas on R...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n418" p="n21" path="Harnessing_the_Power_of_Digital_Data_for_Science_and_Society/" cd="0"&gt;&lt;a href="Harnessing_the_Power_of_Digital_Data_for_Science_and_Society" title="Harnessing the Power of Digital Data for Science and Society"&gt;&lt;span&gt;Harnessing the Powe...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n75" p="n21" path="Interagency_Forum_on_Data_Preservation,_Stewardship,_and_LifeCycle_ESIP_Federation_Meeting,_January_8,_2009/"&gt;&lt;a href="Interagency_Forum_on_Data_Preservation%2c_Stewardship%2c_and_LifeCycle_ESIP_Federation_Meeting%2c_January_8%2c_2009" title="Interagency Forum on Data Preservation, Stewardship, and LifeCycle ESIP Federation Meeting, January 8, 2009"&gt;&lt;span&gt;Interagency Forum o...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n73" p="n21" path="Interagency_Working_Group_on_Digitial_Data/" cd="0"&gt;&lt;a href="Interagency_Working_Group_on_Digitial_Data" title="Interagency Working Group on Digitial Data"&gt;&lt;span&gt;Interagency Working...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n654" p="n21" path="June_4,_2009_How_Does_Government_Become_an_Open_Platform?/"&gt;&lt;a href="June_4%2c_2009_How_Does_Government_Become_an_Open_Platform%3f" title="June 4, 2009 How Does Government Become an Open Platform?"&gt;&lt;span&gt;June 4, 2009 How Do...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1883" p="n21" path="Labor's_Enforcement_Data_Catalog/"&gt;&lt;a href="Labor's_Enforcement_Data_Catalog" title="Labor's Enforcement Data Catalog"&gt;&lt;span&gt;Labor's Enforcement...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling moreNodes" id="n534" p="n21" path="May_13,_2009_Semantic_Web_Meetup/" content="May 13, 2009 Seman..." contentTitle="May 13, 2009 Semantic Web Meetup" hiddenNodes="n2368,n704,n661,n653,n711,n1473,n2352,n427,n1140,n2287,n581,n695,n1935,n1134,n500,n2359,n1757"&gt;&lt;a href="May_13%2c_2009_Semantic_Web_Meetup" title="More..."&gt;&lt;span class="more"&gt;...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2368" p="n21" path="Model_for_Performance-Driven_Government/" cd="0"&gt;&lt;a href="Model_for_Performance-Driven_Government" title="Model for Performance-Driven Government"&gt;&lt;span&gt;Model for Performan...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n704" p="n21" path="NIEM/"&gt;&lt;a href="NIEM" title="NIEM"&gt;&lt;span&gt;NIEM&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n661" p="n21" path="Open_Group_Enterprise_Vocabularly_Workshop_June_3,_2009/"&gt;&lt;a href="Open_Group_Enterprise_Vocabularly_Workshop_June_3%2c_2009" title="Open Group Enterprise Vocabularly Workshop June 3, 2009"&gt;&lt;span&gt;Open Group Enterpri...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n653" p="n21" path="Open_Group_Enterprise_Vocabulary_Workshop_May_20,_2009/"&gt;&lt;a href="Open_Group_Enterprise_Vocabulary_Workshop_May_20%2c_2009" title="Open Group Enterprise Vocabulary Workshop May 20, 2009"&gt;&lt;span&gt;Open Group Enterpri...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n711" p="n21" path="Page_Title/"&gt;&lt;a href="Page_Title" title="Open Government Directive Workshop, January 11, 2010"&gt;&lt;span&gt;Open Government Di...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1473" p="n21" path="Scientific_Data_Management_for_Government_Agencies/"&gt;&lt;a href="Scientific_Data_Management_for_Government_Agencies" title="Scientific Data Management for Government Agencies"&gt;&lt;span&gt;Scientific Data Mana...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2352" p="n21" path="Semantic_eScience/" cd="0"&gt;&lt;a href="Semantic_eScience" title="Semantic eScience"&gt;&lt;span&gt;Semantic eScience&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n427" p="n21" path="Statistical_Abstract_of_the_United_States:_2009/" cd="0"&gt;&lt;a href="Statistical_Abstract_of_the_United_States%3a_2009" title="Statistical Abstract of the United States: 2009"&gt;&lt;span&gt;Statistical Abstract ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n1140" p="n21" path="Statistics/" cd="0"&gt;&lt;a href="Statistics" title="Statistics"&gt;&lt;span&gt;Statistics&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2287" p="n21" path="Survey_of_EPA_and_Other_Federal_Agency_Scientific_Data_Management_Policies_and_Guidance_2010/" cd="0"&gt;&lt;a href="Survey_of_EPA_and_Other_Federal_Agency_Scientific_Data_Management_Policies_and_Guidance_2010" title="Survey of EPA and Other Federal Agency Scientific Data Management Policies and Guidance 2010"&gt;&lt;span&gt;Survey of EPA and O...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n581" p="n21" path="The_Recovery_Dialogue_on_IT_Solutions/" cd="0"&gt;&lt;a href="The_Recovery_Dialogue_on_IT_Solutions" title="The Recovery Dialogue on IT Solutions"&gt;&lt;span&gt;The Recovery Dialog...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n695" p="n21" path="Tools_for_linked_data_from_DERI/"&gt;&lt;a href="Tools_for_linked_data_from_DERI" title="Tools for linked data from DERI"&gt;&lt;span&gt;Tools for linked dat...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1935" p="n21" path="Top_Secret_America/"&gt;&lt;a href="Top_Secret_America" title="Top Secret America"&gt;&lt;span&gt;Top Secret America&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n1134" p="n21" path="Ucore-SL/" cd="0"&gt;&lt;a href="Ucore-SL" title="Ucore-SL"&gt;&lt;span&gt;Ucore-SL&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n500" p="n21" path="W3C_eGovernment_Interest_Group/" cd="0"&gt;&lt;a href="W3C_eGovernment_Interest_Group" title="W3C eGovernment Interest Group"&gt;&lt;span&gt;W3C eGovernment In...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n2359" p="n21" path="Watershed_Boundary_Dataset/"&gt;&lt;a href="Watershed_Boundary_Dataset" title="Watershed Boundary Dataset"&gt;&lt;span&gt;Watershed Boundary ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1757" p="n21" path="White_House_Salaries/"&gt;&lt;a href="White_House_Salaries" title="White House Salaries"&gt;&lt;span&gt;White House Salarie...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;				&lt;div class="navPost"&gt;&lt;/div&gt;
					
				&lt;div class="custom"&gt;
									&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="siteNavPost"&gt;&lt;/div&gt;
		&lt;/div&gt;
				
		&lt;div class="body"&gt;
			&lt;div class="bodyHeader"&gt;
				&lt;div class="pre"&gt;&lt;/div&gt;
				&lt;div class="post"&gt;&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="page"&gt;
				&lt;!-- required print options --&gt;
								
				&lt;div class="custom custom1"&gt;
								&lt;/div&gt;
				
				&lt;div class="siteNav"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
						
	&lt;div class="siteSearch"&gt;
		&lt;fieldset class="search"&gt;
	 		&lt;form action="Special:Search"&gt;
		        &lt;span&gt;Search: &lt;/span&gt;&lt;input id="searchInput" class="inputText" name="search" type="text" value="" /&gt;
				&lt;input type="hidden" name="type" value="fulltext" /&gt;
		        &lt;input type="submit" name="go" class="inputSubmit" value="Find" /&gt;
			&lt;/form&gt;
		&lt;/fieldset&gt;
	&lt;/div&gt;
					
					&lt;ul&gt;
						&lt;li class="userPage"&gt;&lt;a href="User:Anonymous"&gt;&lt;span&gt;&lt;/span&gt;My Page&lt;/a&gt;&lt;/li&gt;
												&lt;li class="siteChanges"&gt;&lt;a href="Special:Recentchanges"&gt;&lt;span&gt;&lt;/span&gt;Recent changes&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteTools"&gt;&lt;a href="#" onclick="return DWMenu.Position('menuTools', this, 0, 0);"&gt;&lt;span&gt;&lt;/span&gt;Tools&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteHelp"&gt;&lt;a href="Resources/Documentation/FAQ/MindTouch_Express"&gt;&lt;span&gt;&lt;/span&gt;Help&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteHelp"&gt;&lt;a href="pro/"&gt;&lt;span&gt;&lt;/span&gt;Go Pro&lt;/a&gt;&lt;/li&gt;					&lt;/ul&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="pageBar"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
					&lt;div class="pageRevision"&gt;
						&lt;!-- last modified --&gt;
						Page last modified &lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=history" title="20:27, 15 Feb 2010"&gt;20:27, 15 Feb 2010&lt;/a&gt; by &lt;a href="User:LucasGraim" class="link-user" rel="internal"&gt;LucasGraim&lt;/a&gt;						&lt;!-- end last modified --&gt;					
					&lt;/div&gt;
					&lt;div class="pageNav"&gt;
						&lt;ul&gt;
							&lt;li class="pageEdit"&gt;&lt;a href="#" title="Edit page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Edit page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageAdd"&gt;&lt;a href="#" title="New page" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;New page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageRestrict"&gt;&lt;a href="#" title="Restrict access" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Restrict access&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageAttach"&gt;&lt;a href="#" title="Attach file" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Attach file&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageMove"&gt;&lt;a href="#" title="Move page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Move page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageDelete"&gt;&lt;a href="#" title="Delete page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Delete page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pagePrint"&gt;&lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=print" title="Print page" onclick="return Print.open('/index.php?title=Blackbook_2_and_3&amp;amp;action=print');" class=""&gt;&lt;span&gt;&lt;/span&gt;Print page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageMore"&gt;&lt;a href="#" onclick="return DWMenu.Position('menuPageOptions', this, 0, 0);"&gt;&lt;span&gt;&lt;/span&gt;More&lt;/a&gt;&lt;/li&gt;
							&lt;li class="navSplit"&gt;&lt;/li&gt;
							&lt;li class="pageToc"&gt;&lt;a href="#" title="Table of contents" onclick="return DWMenu.Position('menuPageContent', this, -2, 0)" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Table of contents&lt;/a&gt;&lt;/li&gt;
						&lt;/ul&gt;
					&lt;/div&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="pageContentFrame"&gt;
				&lt;div class="custom custom4"&gt;
								&lt;/div&gt;
				
				&lt;div id="pageContent" class="pageContent"&gt;
							 				&lt;div class="hierarchy"&gt;
		 					&lt;span class="dw-hierarchy"&gt;&lt;a href=""&gt;Federal Data Web 2.0 Wiki Pilot&lt;/a&gt; &amp;gt; Blackbook 2 and 3&lt;/span&gt;		 				&lt;/div&gt;
	 								
										&lt;div class="pageTitle"&gt;
												&lt;h1 id="title"&gt;&lt;span  class="pageRestricted" &gt;Blackbook 2 and 3&lt;/span&gt;&lt;/h1&gt;
					&lt;/div&gt;
					
								
					&lt;div class="pageStatus"&gt;
 					     					&lt;/div&gt;
 					
 							
					&lt;div class="PageDW-Blackbook2and3"&gt;								
	 				&lt;div id="page-top"&gt;&lt;div id="pageToc"&gt;&lt;div class="pageToc"&gt;&lt;h5&gt;Table of contents&lt;/h5&gt;&lt;em&gt;No headers&lt;/em&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="pageText" id="pageText"&gt; &lt;p&gt;NSA&amp;rsquo;s Blackbook 2 and 3 - The Standard in Semantic Web Technology for Data Management:&lt;/p&gt; &lt;p&gt;Blackbook2 is a project architected by Intervise&amp;rsquo;s Chief Technology Officer (Scott Streit), which moved into open source on September 1, 2009. Blackbook2 is a standard for semantic web processing and is currently used, in production or pilots, at the Department of Defense, Dole Foods, and the Environmental Protection Agency, just to name a few. Without changing Blackbook2, merely adding new data, Blackbook2 processes anything from Shipping Visibility Data to classified, analytical processing.&lt;/p&gt; &lt;p&gt;For &lt;a class=" external" rel="external nofollow" target="_blank" href="" title="http://www.resumesplanet.com"&gt; resume writers&lt;/a&gt;, web application framework for data analysis, Blackbook2's architecture provides secure support for visualization, transformation, data source integration, asynchronous operations, and is vocabulary agnostic. Application programming interfaces (APIs) exist for plugin components that visualize, discover, transform, extract, enrich, or filter graph&amp;#8208;based data such as social networks. Data sources of many types (RDBMs, Documents, RSS) can be mapped into Blackbook2 as RDF/OWL, either by Ingest or real-time mapping solutions such as D2RQ.&lt;/p&gt; &lt;p&gt;The Blackbook2 architecture provides asynchronous operations via a message bus backend so that results are provided just-in-time to real&amp;#8208;time users or to workflows that may run for hours. Blackbook2 is vocabulary agnostic: it can provide mapping to a common ontology for all data sources or it can accommodate disparate vocabularies with common vocabulary subsets (e.g., Dublin Core, VCard). Finally, Blackbook2 is accredited for multi-level security via role-based access and provides integrated logging via standard interfaces (JAAS and Log4J).&lt;/p&gt; &lt;p&gt;Blackbook 2, and now 3, is available free to Federal government employees and is currently running on the NSA CloudBase Cloud Computing Platform. Software, documentation, and collaboration are available at &lt;a class="external" rel="external nofollow" target="_blank" href="wiki/index.php/Main_Page" title="http://rabasrv.jhuapl.edu/wiki/index.php/Main_Page"&gt;http://rabasrv.jhuapl.edu/wiki/index.php/Main_Page&lt;/a&gt;&amp;nbsp; by contacting Buster Fields at &lt;a class="link-mailto" rel="external nofollow" target="_blank" href="mailto:hlfield@nsa.gov" title="mailto:hlfield@nsa.gov"&gt;hlfield@nsa.gov&lt;/a&gt; .&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="printfooter" id="printfooter"&gt;&lt;hr /&gt;
&lt;p&gt;Retrieved from "&lt;a href="Blackbook_2_and_3"&gt;http://federaldata.Wik.is/Blackbook_2_and_3&lt;/a&gt;"&lt;/p&gt;
&lt;/div&gt;
	 				&lt;/div&gt;
				&lt;/div&gt;
				&lt;/div&gt;
				&lt;div class="DW-clear"&gt;&lt;/div&gt;
								&lt;div class="pageInfo"&gt;
					&lt;dl&gt;
						&lt;dt class="pageTags"&gt;&lt;span&gt;&lt;/span&gt;Tag page&lt;/dt&gt;
						&lt;dd class="pageTags"&gt;
			 				&lt;div id="pageTags"&gt;&lt;div class="pageTagList"&gt;&lt;div class="item taglist"&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;		 				&lt;/dd&gt;
						
						&lt;dt class="pageIncomingLinks"&gt;&lt;span&gt;&lt;/span&gt;What links here&lt;/dt&gt;
						&lt;dd class="pageIncomingLinks"&gt;&lt;/dd&gt;
					&lt;/dl&gt;
				&lt;/div&gt;
				
								
				&lt;div class="file"&gt;
					&lt;h2&gt;Files 0&lt;/h2&gt;
					&lt;div class="fileAdd"&gt;
						&lt;a href="Blackbook_2_and_3" class="disabled" onclick="return false"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="attach" alt="" /&gt;&lt;/span&gt;&lt;span class="text"&gt;Attach file or image&lt;/span&gt;&lt;/a&gt;					&lt;/div&gt;
					&lt;div class="fileList"&gt;
		 				&lt;div id="pageFiles"&gt;&lt;div class="nofiles"&gt;&amp;nbsp;&lt;/div&gt;&lt;/div&gt;					&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="gallery"&gt;
					&lt;h2&gt;Images 0&lt;/h2&gt;
	 				&lt;div id="pageGalleryWrap"&gt;&lt;div class="nofiles"&gt;&amp;nbsp;&lt;/div&gt;&lt;/div&gt;				&lt;/div&gt;
				
 				&lt;div id="comments"&gt;&lt;div class="comments"&gt;&lt;div class="commentMore"&gt;Viewing 15 of 143 comments: &lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;commentcount=all#comments" onclick="return MTComments.GetComments('all');" id="commentViewAll"&gt;view all&lt;/a&gt;&lt;/div&gt;&lt;div class="comment" id="comment179"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment179"&gt;#179&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm179"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText179"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment177"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment177"&gt;#177&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm177"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText177"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment176"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment176"&gt;#176&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm176"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText176"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment184"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment184"&gt;#184&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm184"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText184"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment183"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment183"&gt;#183&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm183"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText183"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment182"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment182"&gt;#182&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm182"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText182"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment181"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment181"&gt;#181&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm181"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText181"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment186"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment186"&gt;#186&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm186"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText186"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment185"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment185"&gt;#185&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm185"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText185"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment192"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment192"&gt;#192&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm192"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText192"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment191"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment191"&gt;#191&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm191"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText191"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment190"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment190"&gt;#190&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm190"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText190"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment189"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment189"&gt;#189&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm189"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText189"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment188"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment188"&gt;#188&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm188"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText188"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment187"&gt;&lt;div class="commentNum"&gt;&lt;a href="Blackbook_2_and_3#comment187"&gt;#187&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ThanksMuch" class="link-user" rel="internal"&gt;ThanksMuch&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm187"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText187"&gt;.&lt;div class="commentPosted"&gt;Posted 15:34, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="commentMore"&gt;Viewing 15 of 143 comments: &lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;commentcount=all#comments" onclick="return MTComments.GetComments('all');" id="commentViewAll"&gt;view all&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="commentForm"&gt;You must &lt;a href="index.php?title=Special:Userlogin&amp;amp;returntotitle=Blackbook+2+and+3"&gt;login&lt;/a&gt; to post a comment.&lt;/div&gt;&lt;/div&gt;								
				&lt;div class="custom custom5"&gt;
									&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="bodyFooter"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;div class="Wik.is"&gt;&lt;div class="poweredBy"&gt;Powered by &lt;a href=""&gt; Wik.is Express: open source enterprise collaboration and wik software&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;
			&lt;div class="sourceforge" style="text-align: center; margin: 8px 0;"&gt;&lt;a href="http://wik.is/"&gt;&lt;img src="http://wik.is/wp-content/uploads/2015/06/logo1.png" alt=" Wik.is" /&gt;&lt;/a&gt;&lt;/div&gt; 		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;


&lt;script type="text/javascript"&gt;var _endtime = new Date().getTime(); var _size = 40215;&lt;/script&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuTools" style="display:none;"&gt;
	&lt;ul&gt;	&lt;li class="siteListRss"&gt;&lt;a href="Special:ListRss" title="RSS feeds"&gt;&lt;span&gt;&lt;/span&gt;RSS feeds&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteListusers"&gt;&lt;a href="User:" title="Users"&gt;&lt;span&gt;&lt;/span&gt;Users&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteListTemplates"&gt;&lt;a href="Template:" title="Templates"&gt;&lt;span&gt;&lt;/span&gt;Templates&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteSitemap"&gt;&lt;a href="Special:Sitemap" title="Sitemap"&gt;&lt;span&gt;&lt;/span&gt;Sitemap&lt;/a&gt;&lt;/li&gt;
	&lt;li class="sitePopularpages"&gt;&lt;a href="Special:Popularpages" title="Popular pages"&gt;&lt;span&gt;&lt;/span&gt;Popular pages&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteAbout"&gt;&lt;a href="Special:About" title="About"&gt;&lt;span&gt;&lt;/span&gt;About&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;	
&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuPageOptions" style="display:none;"&gt;
	&lt;ul&gt;	&lt;li class="pageEdit disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Edit page"&gt;&lt;span&gt;&lt;/span&gt;Edit page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageAdd disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');" title="New page"&gt;&lt;span&gt;&lt;/span&gt;New page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageRestrict disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Restrict access"&gt;&lt;span&gt;&lt;/span&gt;Restrict access&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageAttach disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Attach file"&gt;&lt;span&gt;&lt;/span&gt;Attach file&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageMove disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Move page"&gt;&lt;span&gt;&lt;/span&gt;Move page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageDelete disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Delete page"&gt;&lt;span&gt;&lt;/span&gt;Delete page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pagePrint "&gt;&lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=print" onclick="menuOff('menuPageOptions');return Print.open('/index.php?title=Blackbook_2_and_3&amp;amp;action=print');" title="Print page"&gt;&lt;span&gt;&lt;/span&gt;Print page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageTags disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Tag"&gt;&lt;span&gt;&lt;/span&gt;Tag&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageEmail disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Email link"&gt;&lt;span&gt;&lt;/span&gt;Email link&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageProperties disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Set page properties"&gt;&lt;span&gt;&lt;/span&gt;Set page properties&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageTalk "&gt;&lt;a href="Talk:Blackbook_2_and_3" onclick="menuOff('menuPageOptions');" title="Talk page"&gt;&lt;span&gt;&lt;/span&gt;Talk page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageWatch "&gt;&lt;a href="index.php?title=Blackbook_2_and_3&amp;amp;action=watch" onclick="menuOff('menuPageOptions');" title="Watch page"&gt;&lt;span&gt;&lt;/span&gt;Watch page&lt;/a&gt;&lt;/li&gt;
&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuBacklink" style="display:none;"&gt;
	&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuPageContent" style="display:none;"&gt;
	&lt;div class="pageToc"&gt;&lt;h5&gt;Table of contents&lt;/h5&gt;&lt;em&gt;No headers&lt;/em&gt;&lt;/div&gt;&lt;/div&gt;


&lt;div class="ui-msg-wrap" id="MTMessage" style="display: none;"&gt;
	&lt;div class="ui-msg ui-errormsg" id="MTMessageStyle"&gt;
		&lt;div class="ui-msg-opt"&gt;
			&lt;ul&gt;
				&lt;li&gt;&lt;a href="#" class="dismiss" onclick="return MTMessage.Hide();"&gt;dismiss message&lt;/a&gt;&lt;/li&gt;
				&lt;li&gt;&lt;a href="#" class="details" id="MTMessageDetailsLink" onclick="return MTMessage.ShowDetails(this);"&gt;view details&lt;/a&gt;&lt;/li&gt;
			&lt;/ul&gt;
			&lt;div class="ui-msg-autoclose"&gt;
				&lt;span id="MTMessageUnpaused" style="display: inline;"&gt;Message will close by itself in &lt;span id="MTMessageTimer"&gt;&lt;/span&gt; seconds&lt;/span&gt;
				&lt;span id="MTMessagePaused" style="display: none;"&gt;Message timer has been stopped&lt;/span&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		&lt;div class="ui-msg-header" id="MTMessageHeader"&gt;&lt;/div&gt;
		&lt;div class="ui-msg-desc" id="MTMessageDesc"&gt;&lt;/div&gt;
		&lt;div class="ui-msg-desc" id="MTMessageDetails" style="display: none;"&gt;
			&lt;p&gt;Viewing Details:&lt;/p&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;&lt;div id="menuFiller"&gt;&lt;/div&gt;&lt;div id="bodyHeight"&gt;&lt;/div&gt;&lt;script src="urchin.js" type="text/javascript"&gt;&lt;/script&gt;
&lt;!-- Served by ec2-75-101-202-187.compute-1.amazonaws.com in 1.69 secs. --&gt;
&lt;!-- /wik/site/settings: 0.75441813468933--&gt;
&lt;!-- /wik/users/=Anonymous: 0.043669939041138--&gt;
&lt;!-- /wik/site/services/1: 0.0053939819335938--&gt;
&lt;!-- /wik/pages/710/contents: 0.022506952285767--&gt;
&lt;!-- /wik/pages/710: 0.061690092086792--&gt;
&lt;!-- /wik/pages/710/comments: 0.6609480381012--&gt;
&lt;!-- /wik/pages/710/security: 0.019191026687622--&gt;
&lt;!-- /wik/site/nav/=Blackbook%2B2%2Band%2B3/full: 0.051814079284668--&gt;
&lt;!-- Total: 1.6196322441101--&gt;
&lt;!-- Real: 1.6196322441101--&gt;

&lt;/body&gt;
  
&lt;/html&gt;</text>
    <sha1>5b468296ab961ef7a839aa679d29fe37445abcaa</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>ToolsforlinkedData</title>
  <ns>0</ns>
  <id>174</id>
  <revision>
    <id>395</id>
    <timestamp>2016-01-13T17:25:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;  &lt;html xmlns="..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="69644" xml:space="preserve">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;
 &lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us" dir=""&gt;
 &lt;head&gt;


    &lt;script type="text/javascript"&gt;var _starttime = new Date().getTime();&lt;/script&gt;
    &lt;meta http-equiv="Content-Type" content="text/html; charset=utf-8" /&gt;
    &lt;meta name="robots" content="index,follow" /&gt;
&lt;link rel="shortcut icon" href="favicon.ico" /&gt;
&lt;meta name="generator" content=" Wik.is" /&gt;
&lt;link rel="search" type="application/opensearchdescription+xml" title="Federal Data Web 2.0 Wiki Pilot Search" href="/@gui/opensearch/description" /&gt;    &lt;title&gt;Tools for linked data from DERI - Federal Data Web 2.0 Wiki Pilot&lt;/title&gt;
    
    &lt;!-- default css --&gt;
    &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/fiesta/_reset.css"/&gt;
    &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/common/css.php" /&gt; &lt;!--[if IE 7]&gt;&lt;style type="text/css"&gt;@import "/skins/common/_ie7.css";&lt;/style&gt;&lt;![endif]--&gt;&lt;!--[if IE 6]&gt;&lt;style type="text/css"&gt;@import "/skins/common/_ie.css";&lt;/style&gt;&lt;![endif]--&gt;    &lt;link rel="stylesheet" type="text/css" media="print" href="skins/common/print.css" /&gt;    
    &lt;!-- default scripting --&gt;
    &lt;script type="text/javascript" src="skins/common/js.php?perms=LOGIN,BROWSE,READ,SUBSCRIBE&amp;amp;lang=en-us"&gt;&lt;/script&gt;    
    &lt;!-- specific screen stylesheets--&gt;
        &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/fiesta/sky-tangerine/css.php"/&gt;
        
    &lt;!-- specific print stylesheets --&gt;
    &lt;link rel="stylesheet" type="text/css" media="print" href="skins/fiesta/print.css" /&gt;
   
    &lt;!-- IE6 &amp; IE7 specific stuff --&gt;
    &lt;!--[if IE]&gt;&lt;meta http-equiv="imagetoolbar" content="no" /&gt;&lt;![endif]--&gt;
    &lt;!--[if IE 6]&gt;&lt;link rel="stylesheet" type="text/css" media="screen" href="/skins/fiesta/sky-tangerine/ie6.php"/&gt;&lt;![endif]--&gt;
    &lt;!--[if IE 7]&gt;&lt;link rel="stylesheet" type="text/css" media="screen" href="/skins/fiesta/sky-tangerine/ie7.php"/&gt;&lt;![endif]--&gt;
    
    	&lt;script type="text/javascript"&gt;

	    _page_redirect = false;
_path_tpl = '/skins/fiesta';
_path_skin = '/skins/fiesta/sky-tangerine';
_path_common = '/skins/common';
_path_icons = '/skins/common/icons';
editToken = 'aa3a21a0d6b7aa203b0560f8ecf41eb5';
_userName = 'Anonymous';
_userId = '2';
var _editor_styles_path = ['/skins/fiesta/_editor.css', '/skins/fiesta/sky-tangerine/_content.css', ''];
_today = '3 Oct 2010';
baseHref = '/web/20101004055757/http://federaldata.Wik.is';
_page_titlePath = '/';
_page_titleName = 'Tools for linked data from DERI';
_page_ID = 695;
_total_images = 6;
contextTopic = 'Tools for linked data from DERI';
_over_storage_quota = false;
saveFlag = false;

	    
		// remote scripting library
		// (c) copyright 2005 modernmethod, inc
		var sajax_debug_mode = false;
		var sajax_request_type = "POST";

		function sajax_debug(text) {
			if (sajax_debug_mode)
				alert("RSD: " + text);
		};

		function sajax_init_object() {
			sajax_debug("sajax_init_object() called..");

			var A = window.XMLHttpRequest ? new XMLHttpRequest() : window.ActiveXObject ? new ActiveXObject("Microsoft.XMLHTTP") : null;
			if (!A)
				sajax_debug("Could not create connection object.");
			return A;
		};
		function _sajax_do_call(x, func_name, args) {
			var i, x, n;
			var uri;
			var post_data;

			uri = "/index.php";
			if (sajax_request_type == "GET") {
				if (uri.indexOf("?") == -1) 
					uri = uri + "?rs=" + encodeURIComponent(func_name);
				else
					uri = uri + "&amp;rs=" + encodeURIComponent(func_name);
				for (i = 0; i &lt; args.length-1; i++) {
				    var a = args[i];
					uri = uri + "&amp;rsargs[]=" + encodeURIComponent(a);
				}
				uri = uri + "&amp;rsrnd=" + new Date().getTime();
				post_data = null;
			} else {
				post_data = "rs=" + func_name;
				for (i = 0; i &lt; args.length-1; i++) {
				    var a = args[i];
					post_data = post_data + "&amp;rsargs[]=" + encodeURIComponent(a);
				}
			}
			x.open(sajax_request_type, uri, true);
			if (sajax_request_type == "POST") {
				x.setRequestHeader("Method", "POST " + uri + " HTTP/1.1");
				x.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
			}
			x.onreadystatechange = function() {
				if (x.readyState != 4) 
					return;
				if (typeof sajax_debug != 'undefined') sajax_debug("received " + x.responseText);

				var status;
				var data = x.responseText.replace(/^\s+/, '');
				status = data.charAt(0);
				data = data.substring(2);
				if (status == "-") 
					alert("Error: " + data);
				else  
					args[args.length-1](data);
			}
			x.send(post_data);
			sajax_debug(func_name + " uri = " + uri + "/post = " + post_data);
			sajax_debug(func_name + " waiting..");
			return x;
		};
		function sajax_do_call(func_name, args) {
			x = sajax_init_object();
			_sajax_do_call(x, func_name, args);
			delete x;
		};

		function x_breadcrumbSet() { sajax_do_call("breadcrumbSet", x_breadcrumbSet.arguments); };
		function x_wfAdminUserForm() { sajax_do_call("wfAdminUserForm", x_wfAdminUserForm.arguments); };
		function x_wfSetUserOption() { sajax_do_call("wfSetUserOption", x_wfSetUserOption.arguments); };
		function x_wfSetRestrictions() { sajax_do_call("wfSetRestrictions", x_wfSetRestrictions.arguments); };
		function x_setUserOption() { sajax_do_call("setUserOption", x_setUserOption.arguments); };
		function x_wfValidateUserOrGroup() { sajax_do_call("wfValidateUserOrGroup", x_wfValidateUserOrGroup.arguments); };
		function x_wfSaveEdit() { sajax_do_call("wfSaveEdit", x_wfSaveEdit.arguments); };
		function x_wfQueryLinks() { sajax_do_call("wfQueryLinks", x_wfQueryLinks.arguments); };
		function x_loadInplaceEditor() { sajax_do_call("loadInplaceEditor", x_loadInplaceEditor.arguments); };
		function x_doSetbaseHref() { sajax_do_call("doSetbaseHref", x_doSetbaseHref.arguments); };
		function x_showFileAttachments() { sajax_do_call("showFileAttachments", x_showFileAttachments.arguments); };
		function x_doSectionEdit() { sajax_do_call("doSectionEdit", x_doSectionEdit.arguments); };
		function x_postComment() { sajax_do_call("postComment", x_postComment.arguments); };
		function x_getComments() { sajax_do_call("getComments", x_getComments.arguments); };
		function x_deleteComment() { sajax_do_call("deleteComment", x_deleteComment.arguments); };
		function x_editComment() { sajax_do_call("editComment", x_editComment.arguments); };
		function x_wfEmailPage() { sajax_do_call("wfEmailPage", x_wfEmailPage.arguments); };
		function x_wfCheckNewTitle() { sajax_do_call("wfCheckNewTitle", x_wfCheckNewTitle.arguments); };
		function x_wfDeleteFile() { sajax_do_call("wfDeleteFile", x_wfDeleteFile.arguments); };
		function x_wfSetPageProperties() { sajax_do_call("wfSetPageProperties", x_wfSetPageProperties.arguments); };
		function x_wfDeleteTopic() { sajax_do_call("wfDeleteTopic", x_wfDeleteTopic.arguments); };
		function x_wfRenameTopic() { sajax_do_call("wfRenameTopic", x_wfRenameTopic.arguments); };
		function x_wfMoveAttachments() { sajax_do_call("wfMoveAttachments", x_wfMoveAttachments.arguments); };
		function x_wfGetAttachmentUrl() { sajax_do_call("wfGetAttachmentUrl", x_wfGetAttachmentUrl.arguments); };
		function x_wfInlineImageGallery() { sajax_do_call("wfInlineImageGallery", x_wfInlineImageGallery.arguments); };
		function x_wfSetFileDescription() { sajax_do_call("wfSetFileDescription", x_wfSetFileDescription.arguments); };
		function x_wfChangeLoginView() { sajax_do_call("wfChangeLoginView", x_wfChangeLoginView.arguments); };
		function x_wfChangeLoginViewToCreate() { sajax_do_call("wfChangeLoginViewToCreate", x_wfChangeLoginViewToCreate.arguments); };
		function x_wfSaveCredsToSession() { sajax_do_call("wfSaveCredsToSession", x_wfSaveCredsToSession.arguments); };
		function x_wfChangeAddServiceView() { sajax_do_call("wfChangeAddServiceView", x_wfChangeAddServiceView.arguments); };
		function x_wfSaveLoginPageCreds() { sajax_do_call("wfSaveLoginPageCreds", x_wfSaveLoginPageCreds.arguments); };
		function x_wfRemindPassword() { sajax_do_call("wfRemindPassword", x_wfRemindPassword.arguments); };
		function x_wfChangeAvailUsersPage() { sajax_do_call("wfChangeAvailUsersPage", x_wfChangeAvailUsersPage.arguments); };
		
	    window.onbeforeunload = checkForChanges;

	    function checkForChanges() {
	        if (saveFlag &amp;&amp; !doCheckChanges(cur_editor)) {
	        	return "You have made changes to the content without saving your changes. Are you sure you want to exit this page?";
	        }
	    }
	    var aLt = new Array();aLt["attach-no-description"] = 'No description'; aLt["cancel"] = 'Cancel'; aLt["comment-delete"] = 'Are you sure you want to delete this comment?'; aLt["gallery-close"] = 'close'; aLt["gallery-next"] = 'next'; aLt["gallery-prev"] = 'prev'; aLt["internal-error"] = 'Sorry, but there was an internal problem - please try again soon.'; aLt["js-label_cancel"] = 'Cancel'; aLt["js-label_save"] = 'Save'; aLt["js-tooltip_cancel"] = 'Exit Without Saving Changes'; aLt["js-tooltip_save"] = 'Save and Exit (Alt+S)'; aLt["ldap-provide-credentials"] = 'Please provide external service login credentials.'; aLt["loading"] = 'Loading...'; aLt["menu-confirm-delete"] = 'Are you sure you want to delete this file?'; aLt["menu-delete-file"] = 'Delete'; aLt["menu-edit-description"] = 'Edit description'; aLt["menu-move-file"] = 'Move'; aLt["menu-previous-versions"] = 'Previous versions'; aLt["menu-view-original"] = 'View original'; aLt["print-end-notes"] = 'Endnotes'; aLt["ready"] = 'Ready'; aLt["submit"] = 'Submit'; aLt["select-files"] = 'Select files...'; aLt["wikibits-attach-another"] = 'Attach another file'; aLt["wikibits-attach-file"] = 'Attach File'; aLt["wikibits-cant-attach-editing"] = 'Sorry, you can\'t attach files while editing a page. Please close the editor first.'; aLt["wikibits-edit-section"] = 'Edit section'; aLt["wikibits-remove-file"] = 'Remove file';  var wfMsg = function (key) { return aLt[key] ? aLt[key] : 'MISSING: ' + key; };var navMaxWidth = 1600;
	//hook in menu clicking events to the document's body
	YAHOO.util.Event.addListener(document, "click", function () { FileMenu.bodyClick(); DWMenu.BodyClick(); });	
	YAHOO.util.Event.onDOMReady(function () { new clientWindow }); 
	
                
		YAHOO.util.Event.onAvailable("siteNavTree", wik.nav.init, wik.nav, true);
		
	
			YAHOO.util.Event.onDOMReady(function() {
			tb_init('a.lightbox, area.lightbox, input.lightbox, a[@rel=awesomebox]');//pass where to apply thickbox
			imgLoader = new Image();// preload image
			imgLoader.src = tb_pathToImage;
		});
		
		YAHOO.util.Event.onDOMReady(function() { 
			MTComments.HookBehavior();
		});
		&lt;/script&gt;
	
	&lt;!-- styles overwritten via control panel - load this css last --&gt;	
	 
&lt;/head&gt;

&lt;body class="  en-us"&gt;


&lt;noscript&gt;This application requires Javascript to be enabled.&lt;/noscript&gt;

&lt;div class="global"&gt;
	&lt;div class="globalWrap"&gt;
		&lt;div class="header"&gt;
		
			&lt;div class="mastPre"&gt;&lt;/div&gt;
			&lt;div class="mast"&gt;
				
				&lt;div class="siteLogo"&gt;
					&lt;a href="" title="Federal Data Web 2.0 Wiki Pilot"&gt;&lt;img src="skins/fiesta/sky-tangerine/logo.png" alt="Federal Data Web 2.0 Wiki Pilot" title="Federal Data Web 2.0 Wiki Pilot"/&gt;&lt;/a&gt;		
				&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="mastPost"&gt;&lt;/div&gt;
			
			&lt;div class="siteNavPre"&gt;&lt;/div&gt;
			&lt;div class="siteNav"&gt;
				&lt;div class="userAuthPre"&gt;&lt;/div&gt;
							&lt;div class="userAuth"&gt;
			&lt;span&gt;Logged in:&lt;/span&gt;			&lt;span&gt;Logged in as:&lt;/span&gt;					
	 		&lt;a href="index.php?title=Special:Userlogin&amp;amp;returntotitle=Tools+for+linked+data+from+DERI" class="userLogin"&gt;Log in&lt;/a&gt;		&lt;/div&gt;
						
									&lt;div class="userAuthPost"&gt;&lt;/div&gt;
				
				&lt;div class="custom custom2"&gt;
									&lt;/div&gt;
				
					
				&lt;div class="navPre"&gt;&lt;/div&gt;
					&lt;div id="siteNavTree"&gt;&lt;div class="node dockedNode homeNode lastDocked parentClosed" id="n21" c="n2348,n710,n70,n542,n497,n1144,n702,n2349,n1437,n2346,n990,n35,n33,n34,n526,n543,n1884,n2412,n46,n842,n498,n418,n75,n73,n654,n1883,n534,n2368,n704,n661,n653,n711,n1473,n2352,n427,n1140,n2287,n581,n695,n1935,n1134,n500,n2359,n1757" path=""&gt;&lt;a href="" title="Federal Data Web 2.0 Wiki Pilot"&gt;&lt;span&gt;Federal Data Web 2....&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling moreNodes" id="n2348" p="n21" path="Analytics/" content="Analytics" contentTitle="Analytics" hiddenNodes="n710,n70,n542,n497,n1144,n702,n2349,n1437,n2346,n990,n35,n33,n34,n526,n543,n1884,n2412,n46"&gt;&lt;a href="Analytics" title="More..."&gt;&lt;span class="more"&gt;...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n710" p="n21" path="Blackbook_2_and_3/"&gt;&lt;a href="Blackbook_2_and_3" title="Blackbook 2 and 3"&gt;&lt;span&gt;Blackbook 2 and 3&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n70" p="n21" path="Blog_(Web_Log)/"&gt;&lt;a href="Blog_(Web_Log)" title="Blog (Web Log)"&gt;&lt;span&gt;Blog (Web Log)&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n542" p="n21" path="Cambridge_Semantics_Recovery.gov/"&gt;&lt;a href="Cambridge_Semantics_Recovery.gov" title="Cambridge Semantics Recovery.gov"&gt;&lt;span&gt;Cambridge Semantic...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n497" p="n21" path="Comments_and_Innovations_for_the_Open_Government_and_Transparency_Directive/"&gt;&lt;a href="Comments_and_Innovations_for_the_Open_Government_and_Transparency_Directive" title="Comments and Innovations for the Open Government and Transparency Directive"&gt;&lt;span&gt;Comments and Innov...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1144" p="n21" path="Data.gov/"&gt;&lt;a href="Data.gov" title="Data.gov Adds Geoviewer"&gt;&lt;span&gt;Data.gov Adds Geovi...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n702" p="n21" path="Data.gov_Concept_of_Operations_v0.7/"&gt;&lt;a href="Data.gov_Concept_of_Operations_v0.7" title="Data.gov Concept of Operations"&gt;&lt;span&gt;Data.gov Concept of...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n2349" p="n21" path="Data.gov_CONOPS/"&gt;&lt;a href="Data.gov_CONOPS" title="Data.gov CONOPS"&gt;&lt;span&gt;Data.gov CONOPS&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1437" p="n21" path="Data.gov%2fsemantic/"&gt;&lt;a href="Data.gov%2f%2fsemantic" title="Data.gov/semantic"&gt;&lt;span&gt;Data.gov/semantic&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2346" p="n21" path="Data_Science/" cd="0"&gt;&lt;a href="Data_Science" title="Data Science"&gt;&lt;span&gt;Data Science&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n990" p="n21" path="Executive_Office_of_the_President_-_OMB_and_NSA_Detail/"&gt;&lt;a href="Executive_Office_of_the_President_-_OMB_and_NSA_Detail" title="Executive Office of the President - OMB and NSA Detail for Data.gov"&gt;&lt;span&gt;Executive Office of ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n35" p="n21" path="Federal_Data_Architecture_Subcommittee_(DAS)/" cd="0"&gt;&lt;a href="Federal_Data_Architecture_Subcommittee_(DAS)" title="Federal Data Architecture Subcommittee (DAS)"&gt;&lt;span&gt;Federal Data Archite...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n33" p="n21" path="Federal_Data_Reference_Model/"&gt;&lt;a href="Federal_Data_Reference_Model" title="Federal Data Reference Model"&gt;&lt;span&gt;Federal Data Refere...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n34" p="n21" path="Federal_Data_Reference_Model_2.0/" cd="0"&gt;&lt;a href="Federal_Data_Reference_Model_2.0" title="Federal Data Reference Model 2.0"&gt;&lt;span&gt;Federal Data Refere...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n526" p="n21" path="Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form/" cd="0"&gt;&lt;a href="Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form" title="Federal Enterprise Architecture Reference Model Revision Submission Form (DRM 3.0)"&gt;&lt;span&gt;Federal Enterprise A...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n543" p="n21" path="Federal_Enterprise_Architecture_Security_and_Privacy_Profile_Version_3.0/" cd="0"&gt;&lt;a href="Federal_Enterprise_Architecture_Security_and_Privacy_Profile_Version_3.0" title="Federal Enterprise Architecture Security and Privacy Profile Version 3.0"&gt;&lt;span&gt;Federal Enterprise A...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1884" p="n21" path="Federal_IT_Dashboard/"&gt;&lt;a href="Federal_IT_Dashboard" title="Federal IT Dashboard"&gt;&lt;span&gt;Federal IT Dashboar...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2412" p="n21" path="Federal_Segment_Architecture_Methodology_Toolkit/" cd="0"&gt;&lt;a href="Federal_Segment_Architecture_Methodology_Toolkit" title="Federal Segment Architecture Methodology Toolkit"&gt;&lt;span&gt;Federal Segment Arc...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n46" p="n21" path="Federal_Semantic_Interoperability_Community_of_Practice_(SICoP)/" cd="0"&gt;&lt;a href="Federal_Semantic_Interoperability_Community_of_Practice_(SICoP)" title="Federal Semantic Interoperability Community of Practice (SICoP)"&gt;&lt;span&gt;Federal Semantic Int...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n842" p="n21" path="FGDC_Standards_WG_meeting_-_February_23,_2010/"&gt;&lt;a href="FGDC_Standards_WG_meeting_-_February_23%2c_2010" title="FGDC Standards WG Meeting - February 23, 2010"&gt;&lt;span&gt;FGDC Standards WG ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n498" p="n21" path="George_Thomas_on_Recovery.gov/"&gt;&lt;a href="George_Thomas_on_Recovery.gov" title="George Thomas on Recovery.gov"&gt;&lt;span&gt;George Thomas on R...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n418" p="n21" path="Harnessing_the_Power_of_Digital_Data_for_Science_and_Society/" cd="0"&gt;&lt;a href="Harnessing_the_Power_of_Digital_Data_for_Science_and_Society" title="Harnessing the Power of Digital Data for Science and Society"&gt;&lt;span&gt;Harnessing the Powe...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n75" p="n21" path="Interagency_Forum_on_Data_Preservation,_Stewardship,_and_LifeCycle_ESIP_Federation_Meeting,_January_8,_2009/"&gt;&lt;a href="Interagency_Forum_on_Data_Preservation%2c_Stewardship%2c_and_LifeCycle_ESIP_Federation_Meeting%2c_January_8%2c_2009" title="Interagency Forum on Data Preservation, Stewardship, and LifeCycle ESIP Federation Meeting, January 8, 2009"&gt;&lt;span&gt;Interagency Forum o...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n73" p="n21" path="Interagency_Working_Group_on_Digitial_Data/" cd="0"&gt;&lt;a href="Interagency_Working_Group_on_Digitial_Data" title="Interagency Working Group on Digitial Data"&gt;&lt;span&gt;Interagency Working...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n654" p="n21" path="June_4,_2009_How_Does_Government_Become_an_Open_Platform?/"&gt;&lt;a href="June_4%2c_2009_How_Does_Government_Become_an_Open_Platform%3f" title="June 4, 2009 How Does Government Become an Open Platform?"&gt;&lt;span&gt;June 4, 2009 How Do...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1883" p="n21" path="Labor's_Enforcement_Data_Catalog/"&gt;&lt;a href="Labor's_Enforcement_Data_Catalog" title="Labor's Enforcement Data Catalog"&gt;&lt;span&gt;Labor's Enforcement...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n534" p="n21" path="May_13,_2009_Semantic_Web_Meetup/"&gt;&lt;a href="May_13%2c_2009_Semantic_Web_Meetup" title="May 13, 2009 Semantic Web Meetup"&gt;&lt;span&gt;May 13, 2009 Seman...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n2368" p="n21" path="Model_for_Performance-Driven_Government/" cd="0"&gt;&lt;a href="Model_for_Performance-Driven_Government" title="Model for Performance-Driven Government"&gt;&lt;span&gt;Model for Performan...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n704" p="n21" path="NIEM/"&gt;&lt;a href="NIEM" title="NIEM"&gt;&lt;span&gt;NIEM&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n661" p="n21" path="Open_Group_Enterprise_Vocabularly_Workshop_June_3,_2009/"&gt;&lt;a href="Open_Group_Enterprise_Vocabularly_Workshop_June_3%2c_2009" title="Open Group Enterprise Vocabularly Workshop June 3, 2009"&gt;&lt;span&gt;Open Group Enterpri...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n653" p="n21" path="Open_Group_Enterprise_Vocabulary_Workshop_May_20,_2009/"&gt;&lt;a href="Open_Group_Enterprise_Vocabulary_Workshop_May_20%2c_2009" title="Open Group Enterprise Vocabulary Workshop May 20, 2009"&gt;&lt;span&gt;Open Group Enterpri...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n711" p="n21" path="Page_Title/"&gt;&lt;a href="Page_Title" title="Open Government Directive Workshop, January 11, 2010"&gt;&lt;span&gt;Open Government Di...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1473" p="n21" path="Scientific_Data_Management_for_Government_Agencies/"&gt;&lt;a href="Scientific_Data_Management_for_Government_Agencies" title="Scientific Data Management for Government Agencies"&gt;&lt;span&gt;Scientific Data Mana...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n2352" p="n21" path="Semantic_eScience/" cd="0"&gt;&lt;a href="Semantic_eScience" title="Semantic eScience"&gt;&lt;span&gt;Semantic eScience&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n427" p="n21" path="Statistical_Abstract_of_the_United_States:_2009/" cd="0"&gt;&lt;a href="Statistical_Abstract_of_the_United_States%3a_2009" title="Statistical Abstract of the United States: 2009"&gt;&lt;span&gt;Statistical Abstract ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n1140" p="n21" path="Statistics/" cd="0"&gt;&lt;a href="Statistics" title="Statistics"&gt;&lt;span&gt;Statistics&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n2287" p="n21" path="Survey_of_EPA_and_Other_Federal_Agency_Scientific_Data_Management_Policies_and_Guidance_2010/" cd="0"&gt;&lt;a href="Survey_of_EPA_and_Other_Federal_Agency_Scientific_Data_Management_Policies_and_Guidance_2010" title="Survey of EPA and Other Federal Agency Scientific Data Management Policies and Guidance 2010"&gt;&lt;span&gt;Survey of EPA and O...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n581" p="n21" path="The_Recovery_Dialogue_on_IT_Solutions/" cd="0"&gt;&lt;a href="The_Recovery_Dialogue_on_IT_Solutions" title="The Recovery Dialogue on IT Solutions"&gt;&lt;span&gt;The Recovery Dialog...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling selected" id="n695" p="n21" path="Tools_for_linked_data_from_DERI/"&gt;&lt;a href="Tools_for_linked_data_from_DERI" title="Tools for linked data from DERI"&gt;&lt;span&gt;Tools for linked dat...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1935" p="n21" path="Top_Secret_America/"&gt;&lt;a href="Top_Secret_America" title="Top Secret America"&gt;&lt;span&gt;Top Secret America&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n1134" p="n21" path="Ucore-SL/" cd="0"&gt;&lt;a href="Ucore-SL" title="Ucore-SL"&gt;&lt;span&gt;Ucore-SL&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n500" p="n21" path="W3C_eGovernment_Interest_Group/" cd="0"&gt;&lt;a href="W3C_eGovernment_Interest_Group" title="W3C eGovernment Interest Group"&gt;&lt;span&gt;W3C eGovernment In...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n2359" p="n21" path="Watershed_Boundary_Dataset/"&gt;&lt;a href="Watershed_Boundary_Dataset" title="Watershed Boundary Dataset"&gt;&lt;span&gt;Watershed Boundary ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1757" p="n21" path="White_House_Salaries/"&gt;&lt;a href="White_House_Salaries" title="White House Salaries"&gt;&lt;span&gt;White House Salarie...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;				&lt;div class="navPost"&gt;&lt;/div&gt;
					
				&lt;div class="custom"&gt;
									&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="siteNavPost"&gt;&lt;/div&gt;
		&lt;/div&gt;
				
		&lt;div class="body"&gt;
			&lt;div class="bodyHeader"&gt;
				&lt;div class="pre"&gt;&lt;/div&gt;
				&lt;div class="post"&gt;&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="page"&gt;
				&lt;!-- required print options --&gt;
								
				&lt;div class="custom custom1"&gt;
								&lt;/div&gt;
				
				&lt;div class="siteNav"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
						
	&lt;div class="siteSearch"&gt;
		&lt;fieldset class="search"&gt;
	 		&lt;form action="Special:Search"&gt;
		        &lt;span&gt;Search: &lt;/span&gt;&lt;input id="searchInput" class="inputText" name="search" type="text" value="" /&gt;
				&lt;input type="hidden" name="type" value="fulltext" /&gt;
		        &lt;input type="submit" name="go" class="inputSubmit" value="Find" /&gt;
			&lt;/form&gt;
		&lt;/fieldset&gt;
	&lt;/div&gt;
					
					&lt;ul&gt;
						&lt;li class="userPage"&gt;&lt;a href="User:Anonymous"&gt;&lt;span&gt;&lt;/span&gt;My Page&lt;/a&gt;&lt;/li&gt;
												&lt;li class="siteChanges"&gt;&lt;a href="Special:Recentchanges"&gt;&lt;span&gt;&lt;/span&gt;Recent changes&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteTools"&gt;&lt;a href="#" onclick="return DWMenu.Position('menuTools', this, 0, 0);"&gt;&lt;span&gt;&lt;/span&gt;Tools&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteHelp"&gt;&lt;a href="Resources/Documentation/FAQ/MindTouch_Express"&gt;&lt;span&gt;&lt;/span&gt;Help&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteHelp"&gt;&lt;a href="pro/"&gt;&lt;span&gt;&lt;/span&gt;Go Pro&lt;/a&gt;&lt;/li&gt;					&lt;/ul&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="pageBar"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
					&lt;div class="pageRevision"&gt;
						&lt;!-- last modified --&gt;
						Page last modified &lt;a href="index.php?title=Tools_for_linked_data_from_DERI&amp;amp;action=history" title="09:24, 10 Feb 2010"&gt;09:24, 10 Feb 2010&lt;/a&gt; by &lt;a href="User:Anry" class="link-user" rel="internal"&gt;Anry&lt;/a&gt;						&lt;!-- end last modified --&gt;					
					&lt;/div&gt;
					&lt;div class="pageNav"&gt;
						&lt;ul&gt;
							&lt;li class="pageEdit"&gt;&lt;a href="#" title="Edit page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Edit page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageAdd"&gt;&lt;a href="#" title="New page" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;New page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageRestrict"&gt;&lt;a href="#" title="Restrict access" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Restrict access&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageAttach"&gt;&lt;a href="#" title="Attach file" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Attach file&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageMove"&gt;&lt;a href="#" title="Move page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Move page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageDelete"&gt;&lt;a href="#" title="Delete page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Delete page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pagePrint"&gt;&lt;a href="index.php?title=Tools_for_linked_data_from_DERI&amp;amp;action=print" title="Print page" onclick="return Print.open('/index.php?title=Tools_for_linked_data_from_DERI&amp;amp;action=print');" class=""&gt;&lt;span&gt;&lt;/span&gt;Print page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageMore"&gt;&lt;a href="#" onclick="return DWMenu.Position('menuPageOptions', this, 0, 0);"&gt;&lt;span&gt;&lt;/span&gt;More&lt;/a&gt;&lt;/li&gt;
							&lt;li class="navSplit"&gt;&lt;/li&gt;
							&lt;li class="pageToc"&gt;&lt;a href="#" title="Table of contents" onclick="return DWMenu.Position('menuPageContent', this, -2, 0)" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Table of contents&lt;/a&gt;&lt;/li&gt;
						&lt;/ul&gt;
					&lt;/div&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="pageContentFrame"&gt;
				&lt;div class="custom custom4"&gt;
								&lt;/div&gt;
				
				&lt;div id="pageContent" class="pageContent"&gt;
							 				&lt;div class="hierarchy"&gt;
		 					&lt;span class="dw-hierarchy"&gt;&lt;a href=""&gt;Federal Data Web 2.0 Wiki Pilot&lt;/a&gt; &amp;gt; Tools for linked data from DERI&lt;/span&gt;		 				&lt;/div&gt;
	 								
										&lt;div class="pageTitle"&gt;
												&lt;h1 id="title"&gt;&lt;span  class="pageRestricted" &gt;Tools for linked data from DERI&lt;/span&gt;&lt;/h1&gt;
					&lt;/div&gt;
					
								
					&lt;div class="pageStatus"&gt;
 					     					&lt;/div&gt;
 					
 							
					&lt;div class="PageDW-ToolsforlinkeddatafromDERI"&gt;								
	 				&lt;div id="page-top"&gt;&lt;div id="pageToc"&gt;&lt;div class="pageToc"&gt;&lt;h5&gt;Table of contents&lt;/h5&gt;&lt;em&gt;No headers&lt;/em&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="pageText" id="pageText"&gt; &lt;p&gt;&lt;font size="2" face="Palatino Linotype"&gt;&lt;span style="font-size: 11pt; font-family: 'palatino linotype';"&gt;Hello, &lt;/span&gt;&lt;/font&gt;&lt;font size="2" face="Palatino Linotype"&gt;&lt;span style="font-size: 11pt; font-family: 'palatino linotype';"&gt;I collected some information about work we do here at DERI (&lt;a class=" external" rel="external nofollow" target="_blank" href="" title="http://www.deri.ie/"&gt;www.deri.ie&lt;/a&gt;) and is related to linked data.&amp;nbsp;&lt;/span&gt;&lt;/font&gt;&lt;font size="2" face="Palatino Linotype"&gt;&lt;span style="font-size: 11pt; font-family: 'palatino linotype';"&gt;Don&amp;rsquo;t hesitate to contact me if you need more information.&lt;/span&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font size="2"&gt;&lt;span lang="EN-IE" style="font-size: 11pt; font-family: 'palatino linotype';"&gt;*Sindice* (&lt;a class=" external" rel="external nofollow" target="_blank" href="" title="http://sindice.com/"&gt;http://sindice.com/&lt;/a&gt;) is the world-leading Web of Data indexer and search engine. It indexes all kind of structured data such as RDF/XML, RDFa, and microformats and offers additionally a set of APIs (&lt;a class=" external" rel="external nofollow" target="_blank" href="developers/" title="http://sindice.com/developers/"&gt;http://sindice.com/developers/&lt;/a&gt;) that allow to use it from 3rd-party applications.&lt;/span&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font size="2"&gt;&lt;span lang="EN-IE" style="font-size: 11pt; font-family: 'palatino linotype';"&gt;*Web Data Inspector* (&lt;a class=" external" rel="external nofollow" target="_blank" href="developers/inspector" title="http://sindice.com/developers/inspector"&gt;http://sindice.com/developers/inspector&lt;/a&gt;) is a debugging and analytics tools that renders all kinds of structured data (RDFa, RDF/XML, etc.) as Sindice sees it, in diverse forms, including the schema level (vocabularies used) and a graph visualisation of the underlying RDF.&lt;/span&gt;&lt;/font&gt;&lt;/p&gt; &lt;div title="Dissertations" style="position: absolute ! important; top: -923px ! important; left: -645px ! important;"&gt; &lt;a rel="dofollow,index,follow" href="prices.php"&gt;purchase essay&lt;/a&gt; &lt;a rel="dofollow,index,follow" href="bookreport.php"&gt;custom written book report&lt;/a&gt; &lt;a rel="dofollow,index,follow" href="customessay.php"&gt;written essay&lt;/a&gt; &lt;a rel="dofollow,index,follow" href=""&gt;essays online&lt;/a&gt; &lt;a rel="dofollow,index,follow" href=""&gt;online writing help&lt;/a&gt; &lt;/div&gt; &lt;div title="Dissertations" style="position: absolute ! important; left: -645px ! important;"&gt; &lt;a rel="dofollow,index,follow" href=""&gt;essay writer&lt;/a&gt; &lt;a rel="dofollow,index,follow" href=""&gt;essay writing help&lt;/a&gt; &lt;a rel="dofollow,index,follow" href="service.php"&gt;professional writing services&lt;/a&gt; &lt;a rel="dofollow,index,follow" href="index.php"&gt;custom written essays&lt;/a&gt; &lt;a rel="dofollow,index,follow" href="order.php"&gt;essays cheap&lt;/a&gt; &lt;/div&gt; &lt;p&gt;&lt;font size="2"&gt;&lt;span lang="EN-IE" style="font-size: 11pt;"&gt;*Sigma* (&lt;a class=" external" rel="external nofollow" target="_blank" href="" title="http://sig.ma/"&gt;http://sig.ma/&lt;/a&gt;) is a Web of Data browser providing live Web views on the Web of Data. It is built on top of Sindice and uses additionally technologies from OKKAM (&lt;a class=" external" rel="external nofollow" target="_blank" href="" title="http://www.okkam.org/"&gt;http://www.okkam.org/&lt;/a&gt;) and Yahoo! BOSS ( &lt;a class=" external" rel="external nofollow" target="_blank" href="search/boss/" title="http://developer.yahoo.com/search/boss/"&gt;http://developer.yahoo.com/search/boss/&lt;/a&gt;). The user interface renders the structured data in a convenient way and additionally reports the origin of the data source so that a human can disambiguate information found on the open Web of Data. Sigma as well offers APIs and embeddable 'live widgets', that is if one of the sources updates its information, the widget is updated as well.&lt;/span&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font size="2"&gt;&lt;span lang="EN-IE" style="font-size: 11pt; font-family: 'palatino linotype';"&gt;*Neologism* (&lt;a class=" external" rel="external nofollow" target="_blank" href="" title="http://neologism.deri.ie/"&gt;http://neologism.deri.ie/&lt;/a&gt;) is a Web-based vocabulary editor based on Drupal. Its main goal is to dramatically reduce the time required to create, publish and modify vocabularies for the Web of Data. It produces RDF Schema-based vocabularies including HTML and RDF representations and provides a graphical visualisation of the so created vocabulary. Example instances run at &lt;a class=" external" rel="external nofollow" target="_blank" href="ns/" title="http://rdfs.org/ns/"&gt;http://rdfs.org/ns/&lt;/a&gt; and &lt;a class=" external" rel="external nofollow" target="_blank" href="ontology/" title="http://imp.deri.ie/ontology/"&gt;http://imp.deri.ie/ontology/&lt;/a&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font size="2"&gt;&lt;span lang="EN-IE" style="font-size: 11pt; font-family: 'palatino linotype';"&gt;* DERI contributed significantly to the Opensource CMS Drupal and modules therein to produce and consume linked open data. Particularly, the rdfcck (&lt;a class=" external" rel="external nofollow" target="_blank" href="project/rdfcck" title="http://drupal.org/project/rdfcck"&gt;http://drupal.org/project/rdfcck&lt;/a&gt;) and evoc (&lt;a class=" external" rel="external nofollow" target="_blank" href="project/evoc" title="http://drupal.org/project/evoc"&gt;http://drupal.org/project/evoc&lt;/a&gt;) modules allow to generate RDF and RDFa from any existing Drupal site, and map it to existing vocabularies on the Web. Additionally, modules for providing a SPARQL endpoint and for including external RDF data buy a SPARQL endpoint have been developed and are ready for use.&lt;/span&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font size="2"&gt;&lt;span lang="EN-IE" style="font-size: 11pt; font-family: 'palatino linotype';"&gt;* XSPARQL (&lt;a class=" external" rel="external nofollow" target="_blank" href="" title="http://xsparql.deri.org/"&gt;http://xsparql.deri.org&lt;/a&gt;) With currently available tools and languages, translating between an existing XML format and RDF is a tedious and error-prone task. The importance of this problem is acknowledged by the W3C GRDDL working group who faces the issue of extracting RDF data out of existing HTML or XML files, as well as by the Web service community around SAWSDL, who need to perform lowering and lifting between RDF data from a semantic client and XML messages for a Web service. However, at the moment, both these groups rely solely on XSLT transformations between RDF/XML and the respective other XML format at hand. We propose a more natural approach for such transformations based on merging XQuery and SPARQL into the novel language XSPARQL. XSPARQL provides concise and intuitive solutions for mapping between XML and RDF in either direction, addressing both the use cases of GRDDL and SAWSDL. An implementation of a XSPARQL engine is available at sourceforge.&lt;/span&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font size="2"&gt;&lt;span lang="EN-IE" style="font-size: 11pt; font-family: 'palatino linotype';"&gt;* The Linked Data Research Centre (LiDRC) (&lt;a class=" external" rel="external nofollow" target="_blank" href="" title="http://linkeddata.deri.ie/"&gt;http://linkeddata.deri.ie/&lt;/a&gt;) is a research centre with the mission to bundle activities around linked data throughout DERI. In the LiDRC several research themes are covered (publishing linked data, discovery, applications, streamed linked data, linked government data) aiming at both research and development. Currently,&lt;/span&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font size="2"&gt;&lt;span lang="EN-IE" style="font-size: 11pt; font-family: 'palatino linotype';"&gt;13 DERI researcher (&lt;a class=" external" rel="external nofollow" target="_blank" href="people" title="http://linkeddata.deri.ie/people"&gt;http://linkeddata.deri.ie/people&lt;/a&gt;] work together with nine peer research groups (&lt;a class=" external" rel="external nofollow" target="_blank" href="peers" title="http://linkeddata.deri.ie/peers"&gt;http://linkeddata.deri.ie/peers&lt;/a&gt;) (incl. Tim Berners-Lee's group at MIT, Jim Hendler at RPI, and Chris Bizer at Freie Universit&amp;auml;t Berlin) to address the challenges of publishing and consuming linked data. Additionally to the R&amp;amp;D work, the LiDRC offers linked data tutorials, as well as tools and libraries around linked data (&lt;a class=" external" rel="external nofollow" target="_blank" href="services" title="http://linkeddata.deri.ie/services"&gt;http://linkeddata.deri.ie/services&lt;/a&gt;).&lt;/span&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font size="2"&gt;&lt;span lang="EN-IE" style="font-size: 11pt; font-family: 'palatino linotype';"&gt;Regards, Vassilios &lt;a class=" link-mailto" rel="external nofollow" target="_blank" href="mailto:vassilios.peristeras@deri.org" title="mailto:vassilios.peristeras@deri.org"&gt;vassilios.peristeras@deri.org&lt;/a&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="printfooter" id="printfooter"&gt;&lt;hr /&gt;
&lt;p&gt;Retrieved from "&lt;a href="Tools_for_linked_data_from_DERI"&gt;http://federaldata.Wik.is/Tools_for_linked_data_from_DERI&lt;/a&gt;"&lt;/p&gt;
&lt;/div&gt;
	 				&lt;/div&gt;
				&lt;/div&gt;
				&lt;/div&gt;
				&lt;div class="DW-clear"&gt;&lt;/div&gt;
								&lt;div class="pageInfo"&gt;
					&lt;dl&gt;
						&lt;dt class="pageTags"&gt;&lt;span&gt;&lt;/span&gt;Tag page&lt;/dt&gt;
						&lt;dd class="pageTags"&gt;
			 				&lt;div id="pageTags"&gt;&lt;div class="pageTagList"&gt;&lt;div class="item taglist"&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;		 				&lt;/dd&gt;
						
						&lt;dt class="pageIncomingLinks"&gt;&lt;span&gt;&lt;/span&gt;What links here&lt;/dt&gt;
						&lt;dd class="pageIncomingLinks"&gt;&lt;/dd&gt;
					&lt;/dl&gt;
				&lt;/div&gt;
				
								
				&lt;div class="file"&gt;
					&lt;h2&gt;Files 0&lt;/h2&gt;
					&lt;div class="fileAdd"&gt;
						&lt;a href="Tools_for_linked_data_from_DERI" class="disabled" onclick="return false"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="attach" alt="" /&gt;&lt;/span&gt;&lt;span class="text"&gt;Attach file or image&lt;/span&gt;&lt;/a&gt;					&lt;/div&gt;
					&lt;div class="fileList"&gt;
		 				&lt;div id="pageFiles"&gt;&lt;div class="nofiles"&gt;&amp;nbsp;&lt;/div&gt;&lt;/div&gt;					&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="gallery"&gt;
					&lt;h2&gt;Images 0&lt;/h2&gt;
	 				&lt;div id="pageGalleryWrap"&gt;&lt;div class="nofiles"&gt;&amp;nbsp;&lt;/div&gt;&lt;/div&gt;				&lt;/div&gt;
				
 				&lt;div id="comments"&gt;&lt;div class="comments"&gt;&lt;div class="commentMore"&gt;Viewing 15 of 177 comments: &lt;a href="index.php?title=Tools_for_linked_data_from_DERI&amp;amp;commentcount=all#comments" onclick="return MTComments.GetComments('all');" id="commentViewAll"&gt;view all&lt;/a&gt;&lt;/div&gt;&lt;div class="comment" id="comment173"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment173"&gt;#173&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:fgermanyer" class="link-user" rel="internal"&gt;fgermanyer&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm173"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText173"&gt;important news for you.  it is a directory of New Zealand government datasets. This directory could also be characterised as a single point of access for governmental datasets since it includes links to other governmental web sites that contain the actual files. 

&lt;a href=""&gt;orlando home insurance provider&lt;/a&gt;&lt;div class="commentPosted"&gt;Posted 13:57, 31 Jul 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment174"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment174"&gt;#174&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;wholesale designer handbags&lt;a href="User:wholesale_designer_handbags" class="new link-user" rel="internal"&gt;?&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm174"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText174"&gt;Authentic designer handbags are attractive to every woman. As most girls have   never even held a job or earned money of their own,it would be ridiculous for   them to even think of spending the sums of money to purchase &lt;A title="replica designer handbags" href=""&gt;&lt;strong&gt;replica designer handbags&lt;/strong&gt;&lt;/A&gt;.   Replica handbags are available at low prices that even many girls are able to   afford.To the women who &lt;A href=""&gt;wholesale designer handbags&lt;/A&gt;, it is clear that shopping fashion   handbags cost much. If you shop online, you will save much. Now there are many   online wholesale replica handbags offering cheap fashion handbags. &lt;A href=""&gt;cheap designer clothes&lt;/A&gt; are waiting for you. Shopping &lt;A href=""&gt;silver 925 jewelry&lt;/A&gt; online also saves you time and energy. You don't   have to spend a large amount of&lt;BR&gt;
time on shopping. Now spring is coming,   fashion handbags will add beauty, comfort and green to your life. Fashion   replica designer handbags and &lt;A title="replica designer sandals" href=""&gt;replica designer sandals&lt;/A&gt; are   the clever choice of women.My Queens Maptote is another favorite since I love &lt;A title="wholesale designer clothing" href=""&gt;wholesale designer clothing&lt;/A&gt; Queens and I want the world to know. I picked silver 925 jewelry , this up from   my local boutique Stray Vintage &amp;amp; More. This bag really works in black   canvas since it really makes the purple print pop.&lt;A title="wholesale designer handbags" href=""&gt;wholesale designer handbags&lt;/A&gt; I   was using this for a gym bag for &lt;A title="cheap designer clothes" href=""&gt;cheap designer clothes&lt;/A&gt; a while   but it was too small to comfortably fit my sneakers.it's a clever choice to our &lt;A title="coach handbags outlet" href="Wholesale-coach-handbags_c966"&gt;coach handbags outlet&lt;/A&gt; store. &lt;div class="commentPosted"&gt;Posted 16:47, 31 Jul 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment175"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment175"&gt;#175&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:sarahs" class="link-user" rel="internal"&gt;sarahs&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm175"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText175"&gt;we get all the information here what we needed , thanks for sharing a beautifull post..

&lt;a href=""&gt;florida health insurance provider&lt;/a&gt;&lt;div class="commentPosted"&gt;Posted 17:05, 31 Jul 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment176"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment176"&gt;#176&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:loans123" class="link-user" rel="internal"&gt;loans123&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm176"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText176"&gt;I was truly amazed by your post.
I think that this is very educational.
You have made many great points here.
I hope to see more of your posts.
Its all very helpful, thanks so much for sharing this.

&lt;a href = ""&gt;Home&lt;/a&gt; | &lt;a href = "ca-homes.html"&gt;Real Estate&lt;/a&gt; | 3.5% FHA | &lt;a href = "featured-listings.html"&gt;Real Estate&lt;/a&gt; | &lt;a href = "forum/"&gt;Real Estate&lt;/a&gt; | 100% VA | &lt;a href = "instant-prequal-and-apply.html"&gt;Mortgage&lt;/a&gt; | &lt;a href = "lending.html"&gt;Mortgage&lt;/a&gt; | Zero Down USDA | &lt;a href = "ca-homes/la-central/366-monterey-park-ca-homes.html"&gt;Monterey Park Real Estate&lt;/a&gt; | &lt;a href = "ca-homes/south-bay/403-saratoga-ca-homes.html"&gt;Saratoga Realtors&lt;/a&gt; | Half Percent Down  | &lt;a href = "ca-homes/san-gabriel-valley/314-el-monte-ca-homes.html"&gt;El Monte Home&lt;/a&gt; | &lt;a href = "ca-homes/peninsula/477-belmont-ca-homes.html"&gt;Belmont House&lt;/a&gt; | 203 K FHA | &lt;a href = "ca-homes/la-west-south-bay/309-gardena-ca-homes.html"&gt;Gardena Real Estate&lt;/a&gt; | &lt;a href = "ca-homes/inland-empire/428-ontario-ca-homes.html"&gt;Ontario Realestate&lt;/a&gt; | Conventional Loans | &lt;a href = "ca-homes/san-diego/733-national-city-ca-homes.html"&gt;National City Homes&lt;/a&gt; | &lt;a href = "ca-homes/peninsula/383-south-san-francisco-ca-homes.html"&gt;South San Francisco Home&lt;/a&gt; | Jumbo Loans | &lt;a href = "ca-homes/bakersfield/737-bakersfield-additional-cities.html"&gt;California City Homes For Sale&lt;/a&gt; | &lt;a href = "ca-homes/stockton/499-tracy-ca-homes.html"&gt;Tracy Houses&lt;/a&gt; | City Down Payment | &lt;a href = "ca-homes/sacramento/247-citrus-heights-ca-homes.html"&gt;Citrus Heights Real Estate&lt;/a&gt; | &lt;a href = "ca-homes/orange/341-ladera-ranch-ca-homes.html"&gt;Ladera Ranch Real Estate&lt;/a&gt; | 2yr BK Discharge OK | &lt;a href = "ca-homes/orange/339-westminster-ca-homes.html"&gt;Westminster Housing&lt;/a&gt; | &lt;a href = "ca-homes/orange/302-orange-ca-homes.html"&gt;Orange California Home&lt;/a&gt; | &lt;620 FICO with No 12 mo lates | &lt;a href = "ca-homes/long-beach/243-long-beach-ca-homes.html"&gt;Long Beach California Homes&lt;/a&gt; | &lt;a href = "ca-homes/east-bay/488-lafayette-ca-homes.html"&gt;Homes in Lafayette&lt;/a&gt; | 620+ FICO Ok | &lt;a href = "ca-homes/east-bay/225-brentwood-ca-homes.html"&gt;Brentwood House&lt;/a&gt; | &lt;a href = "ca-homes/slo-sb-santa-maria/760-slo-sb-santa-maria-additional-cities.html"&gt;Solvang House&lt;/a&gt; | 6% Seller Credit OK | &lt;a href = "ca-homes/san-diego/753-san-diego-imperial-additional-cities.html"&gt;Fallbrook Homes&lt;/a&gt; | &lt;a href = "ca-homes/la-central/744-la-central-additional-cities.html"&gt;La Habra Heights Home&lt;/a&gt; | 30 Yr Fixed | &lt;a href = "ca-homes/fresno-madera/739-fresno-madera-additional-cities.html"&gt;Hanford Real Estate&lt;/a&gt; | &lt;a href = "ca-homes/south-bay/398-los-gatos-ca-homes.html"&gt;Los Gatos Houses&lt;/a&gt; | 15 Yr Fixed | &lt;a href = "ca-homes/sf-valley/241-lancaster-ca-homes.html"&gt;Houses In Lancaster&lt;/a&gt; | &lt;a href = "ca-homes/san-gabriel-valley/450-claremont-ca-homes.html"&gt;Claremont Homes For Sale&lt;/a&gt; | 20 Yr Fixed | &lt;a href = "ca-homes/peninsula/479-foster-city-ca-homes.html"&gt;Foster City Homes&lt;/a&gt; | &lt;a href = "ca-homes/orange/313--yorba-linda-ca-homes.html"&gt;Yorba Linda Homes Sale&lt;/a&gt; | 5 Yr Adjustable | &lt;a href = "ca-homes/long-beach/456-la-mirada-ca-homes.html"&gt;La Mirada Houses&lt;/a&gt; | &lt;a href = "ca-homes/orange/302-orange-ca-homes.html"&gt;Orange Foreclosures&lt;/a&gt; | 7 Yr Adjustable | &lt;a href = "ca-homes/inland-empire/441-rialto-ca-homes.html"&gt;Rialto Homes For Sale&lt;/a&gt; | &lt;a href = "ca-homes/east-bay/319-altadena-ca-homes.html"&gt;Altadena Real Estate&lt;/a&gt; | 10 Yr Adjustable &lt;div class="commentPosted"&gt;Posted 11:32, 1 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment177"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment177"&gt;#177&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:fang" class="link-user" rel="internal"&gt;fang&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm177"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText177"&gt;&lt;p&gt;&lt;strong&gt;&lt;strong&gt;Buy &lt;a href=""&gt;MBT Shoes&lt;/a&gt;!&lt;a href=""&gt;MBT shoes sale&lt;/a&gt; online now at http://www.vogueforever.com you will find the best prices in &lt;a href=""&gt;mbt shoes clearance&lt;/a&gt; and we offer &lt;a href="mbt-staka-sandal-c-862.html"&gt;MBT Staka Sandal&lt;/a&gt;|&lt;a href="mbt-salama-sandal-c-861.html"&gt;MBT Salama Sandal&lt;/a&gt;|&lt;a href="mbt-panda-sandal-c-870.html"&gt;MBT Panda Sandal&lt;/a&gt;|&lt;a href="mbt-imara-sandal-c-863.html"&gt;MBT Imara Sandal&lt;/a&gt;|&lt;a href="mbt-baridi-shoes-c-872.html"&gt;MBT Baridi Shoes&lt;/a&gt;|&lt;a href="mbt-ema-sandal-c-860.html"&gt;MBT EMA Sandal&lt;/a&gt;|&lt;a href="mbt-tataga-c-848.html"&gt;MBT Tataga&lt;/a&gt;|&lt;a href="mbt-fanaka-gtx-c-841.html"&gt;MBT Fanaka GTX&lt;/a&gt;|&lt;a href="mbt-mens-fumba-cinnebar-brown-leather-p-17689.html"&gt;MBT Fumba&lt;/a&gt;|&lt;a href="mbt-maliza-c-845.html"&gt;MBT Maliza&lt;/a&gt;|&lt;a href="mbt-safiri-c-846.html"&gt;MBT Safiri&lt;/a&gt;|&lt;a href="mbt-shuguli-c-847.html"&gt;MBT Shuguli&lt;/a&gt;|&lt;a href="mbt-tembea-c-849.html"&gt;MBT Tembea&lt;/a&gt;|&lt;a href="mbt-tunisha-c-850.html"&gt;MBT Tunisha&lt;/a&gt;|&lt;a href="mbt-voi-c-851.html"&gt;MBT Voi&lt;/a&gt;|&lt;a href="mbt-barabara-c-839.html"&gt;MBT Barabara&lt;/a&gt;|&lt;a href="mbt-boost-c-840.html"&gt;MBT Boost&lt;/a&gt;|&lt;a href="mbt-changa-c-836.html"&gt;MBT Changa&lt;/a&gt;|&lt;a href="mbt-chapa-c-835.html"&gt;MBT Chapa&lt;/a&gt;|&lt;a href="mbt-fora-c-837.html"&gt;MBT Fora&lt;/a&gt;|&lt;a href="mbt-habari-c-859.html"&gt;MBT Habari&lt;/a&gt;|&lt;a href="mbt-karani-c-857.html"&gt;MBT Karani&lt;/a&gt;|&lt;a href="mbt-kaya-c-844.html"&gt;MBT Kaya&lt;/a&gt;|&lt;a href="mbt-kisumu-c-858.html"&gt;MBT Kisumu&lt;/a&gt;|&lt;a href="mbt-lami-c-3.html"&gt;MBT Lami&lt;/a&gt;|&lt;a href="mbt-mwalk-c-1.html"&gt;MBT M.Walk&lt;/a&gt;|&lt;a href="mbt-moto-goretex-black-nubuck-waterproof-mens-p-17694.html"&gt;MBT Moto GTX&lt;/a&gt;|&lt;a href="mbt-sapatu-c-854.html"&gt;MBT Sapatu&lt;/a&gt;|&lt;a href="mbt-sport-2-c-834.html"&gt;MBT Sport 2&lt;/a&gt;|&lt;a href="mbt-tariki-c-852.html"&gt;MBT Tariki&lt;/a&gt;
up to 70% off with free shipping ( Not All ).&lt;a href="mbt-fora-c-837.html"&gt;MBT Fora shoes&lt;/a&gt;!&lt;a href="vibram-five-finger-shoes-c-881.html"&gt;Vibram Five Finger Shoes&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;&lt;div class="commentPosted"&gt;Posted 09:28, 2 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment178"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment178"&gt;#178&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:sarahs" class="link-user" rel="internal"&gt;sarahs&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm178"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText178"&gt;This kind of articles brings a good motion towards the audience , great content here everyone should appreciate their work as well , thanks for sharing..
&lt;a href=""&gt;Marketing Research Firm&lt;/a&gt;&lt;div class="commentPosted"&gt;Posted 05:27, 3 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment179"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment179"&gt;#179&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:sarahs" class="link-user" rel="internal"&gt;sarahs&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm179"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText179"&gt;Mutual and great content here it is according to the post, thanks for sharing ..


&lt;a href=""&gt;federal grants small business&lt;/a&gt;&lt;div class="commentPosted"&gt;Posted 11:03, 4 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment180"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment180"&gt;#180&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:tresedered" class="link-user" rel="internal"&gt;tresedered&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm180"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText180"&gt;I Need more and more information regarding this post , thanks for sharing this..

&lt;a href=""&gt;education foundation grants&lt;/a&gt;&lt;div class="commentPosted"&gt;Posted 04:30, 6 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment181"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment181"&gt;#181&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ddoelsenf" class="link-user" rel="internal"&gt;ddoelsenf&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm181"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText181"&gt;Maintain all the deri  sites greatly in the web , i need more information please tell me where can i get it..
&lt;a href=""&gt;california motorcycle insurance&lt;/a&gt;
&lt;div class="commentPosted"&gt;Posted 04:39, 7 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment182"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment182"&gt;#182&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:ghdshopbar" class="link-user" rel="internal"&gt;ghdshopbar&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm182"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText182"&gt;Do you have a lot of trouble styling your hair? You may want to consider getting a &lt;a href=""&gt;&lt;strong&gt;GHD hair straightener&lt;/strong&gt;&lt;/a&gt;. 
Buy cheap ghd hair straighteners on &lt;a href=""&gt;&lt;strong&gt;ghdshopbar.com&lt;/strong&gt;&lt;/a&gt;
&lt;a href="products_new.html"&gt;&lt;strong&gt;New GHD Products&lt;/strong&gt;&lt;/a&gt;
&lt;a href="specials.html"&gt;&lt;strong&gt;Special GHD Products&lt;/strong&gt;&lt;/a&gt;
&lt;a href="chi-flat-irons-wholesale-19.html"&gt;&lt;strong&gt;CHI Flat Irons&lt;/strong&gt;&lt;/a&gt;
&lt;a href="chi-hair-dryer-wholesale-20.html"&gt;&lt;strong&gt;CHI Hair Dryer&lt;/strong&gt;&lt;/a&gt;
&lt;a href="ghd-limited-edition-dark-product-6.html"&gt;&lt;em&gt;GHD Dark&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-iv-mk4-gold-hair-straightener-flat-product-2.html"&gt;&lt;em&gt;GHD IV MK4 Gold Hair Straightener&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-black-flat-iron-product-26.html"&gt;&lt;em&gt;CHI Black Flat iron&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-digital-ceramic-flat-iron-product-28.html"&gt;&lt;em&gt;CHI Digital Ceramic Flat Iron&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-pink-dazzle-flat-iron-product-30.html"&gt;&lt;em&gt;CHI Pink Dazzle Flat Iron&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-babyliss-pro-230-radiance-product-12.html"&gt;&lt;em&gt;GHD Babyliss&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-black-limited-edition-mk4-hair-straightener-product-1.html"&gt;&lt;em&gt;GHD Black MK4 Hair Straightener&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-blue-nano-ceramic-flat-iron-product-29.html"&gt;&lt;em&gt;CHI Blue Nano Ceramic Flat Iron&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-camo-collection-blue-product-31.html"&gt;&lt;em&gt;CHI Camo Collection Blue&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-camo-collection-green-product-33.html"&gt;&lt;em&gt;CHI Camo Collection Green&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-camo-collection-pink-product-32.html"&gt;&lt;em&gt;CHI Camo Collection Pink&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-iv-mk4-pink-hair-straightener-flat-product-3.html"&gt;&lt;em&gt;GHD IV Mk4 Pink&lt;/em&gt;&lt;/a&gt;
&lt;a href="09-new-style-ghd-pink-hair-straightener-product-9.htm"&gt;&lt;em&gt;New Style GHD Pink Hair Straightener&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-pure-iv-mk4-hair-straightener-product-7.html"&gt;&lt;em&gt;Pure GHD&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-iv-mk4-salon-styler-product-4.html"&gt;&lt;em&gt;New GHD 2010&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-pink-flat-iron-product-27.html"&gt;&lt;em&gt;CHI Pink Flat Iron&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-turbo-ceramic-hairstyling-iron-1-product-34.html"&gt;&lt;em&gt;CHI Turbo Ceramic Hairstyling Iron 1&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-turbo-ceramic-hairstyling-iron-2-product-35.html"&gt;&lt;em&gt;CHI Turbo Ceramic Hairstyling Iron 2&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-iv-mk4-salon-styler-product-4.html"&gt;&lt;em&gt;GHD IV MK4 Salon&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-purple-hair-straightener-product-8.html"&gt;&lt;em&gt;GHD IV Styler Purple&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-limited-edition-precious-gift-set-product-14.html"&gt;&lt;em&gt;GHD Limited Edition Precious Gift Set&lt;/em&gt;&lt;/a&gt;
&lt;a href="new-ghd-rare-limited-edition-iv-styler-gift-set-product-17.html"&gt;&lt;em&gt;New GHD Rare Limited Edition IV Styler&lt;/em&gt;&lt;/a&gt;
&lt;a href="wee-chi-ceramic-flat-iron-product-36.html"&gt;&lt;em&gt;WEE CHI Ceramic Flat Iron&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-nano-ceramic-hair-dryer-black-product-23.html"&gt;&lt;em&gt;CHI Nano Ceramic Hair Dryer Black&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-nano-ceramic-hair-dryer-blue-product-24.html"&gt;&lt;em&gt;CHI Nano Ceramic Hair Dryer Blue&lt;/em&gt;&lt;/a&gt;
&lt;a href="chi-nano-ceramic-hair-dryer-red-product-25.html"&gt;&lt;em&gt;CHI Nano Ceramic Hair Dryer Red&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-iv-mk4-kiss-hair-straightener-product-10.html"&gt;&lt;em&gt;GHD Kiss&lt;/em&gt;&lt;/a&gt;
&lt;a href="ghd-iv-mini-styler-hair-straightener-product-18.html"&gt;&lt;em&gt;ghd IV Mini Styler&lt;/em&gt;&lt;/a&gt;&lt;div class="commentPosted"&gt;Posted 15:23, 11 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment183"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment183"&gt;#183&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:uggsw" class="link-user" rel="internal"&gt;uggsw&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm183"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText183"&gt;&lt;p&gt;&lt;a href=""&gt;&lt;strong&gt;Uggs&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=""&gt;&lt;strong&gt;UGG Boots&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=""&gt;&lt;strong&gt;Ugg Sale&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=""&gt;&lt;strong&gt;Cheap Ugg Boots&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=""&gt;&lt;strong&gt;Discount UGG Boots&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=""&gt;&lt;strong&gt;UGG Boots Sale&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;A href="ugg-bailey-button-c-241.html"&gt;&lt;strong&gt;Ugg   Bailey Button&lt;/strong&gt;&lt;/A&gt;&lt;/p&gt;
&lt;p&gt;&lt;A href="ugg-classic-argyle-knit-c-238.html"&gt;&lt;strong&gt;Ugg   Classic Argyle Knit&lt;/strong&gt;&lt;/A&gt;&lt;/p&gt;
&lt;p&gt;&lt;A href="ugg-classic-cardy-c-240.html"&gt;&lt;strong&gt;Ugg   Classic Cardy&lt;/strong&gt;&lt;/A&gt;&lt;/p&gt;
&lt;p&gt;&lt;A href="ugg-classic-crochet-c-252.html"&gt;&lt;strong&gt;Ugg   Classic Crochet&lt;/strong&gt;&lt;/A&gt;&lt;/p&gt;
&lt;p&gt;&lt;A href="ugg-classic-mini-c-244.html"&gt;&lt;strong&gt;Ugg   Classic Mini&lt;/strong&gt;&lt;/A&gt;&lt;/p&gt;
&lt;p&gt;&lt;A href="ugg-classic-short-c-242.html"&gt;&lt;strong&gt;Ugg   Classic Short&lt;/strong&gt;&lt;/A&gt;&lt;/p&gt;
&lt;p&gt;&lt;A href="ugg-classic-tall-c-239.html"&gt;&lt;strong&gt;Ugg   Classic Tall&lt;/strong&gt;&lt;/A&gt;&lt;/p&gt;
&lt;p&gt;&lt;A href="ugg-classic-tall-stripe-c-248.html"&gt;&lt;strong&gt;Ugg   Classic Tall Stripe&lt;/strong&gt;&lt;/A&gt;&lt;/p&gt;
&lt;p&gt;&lt;A href="ugg-coquette-c-253.html"&gt;&lt;strong&gt;Ugg   Coquette&lt;/strong&gt;&lt;/A&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="STYLE1"&gt;&lt;A href="ugg-gypsy-sandal-c-254.html"&gt;Ugg   Gypsy Sandal&lt;/A&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;A href="ugg-brown-summer-fashion-female-sandal-p-6122.html"&gt;Ugg   Halendi Sandal&lt;/A&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;A href="ugg-lo-pro-button-c-256.html"&gt;Ugg   Lo Pro Button&lt;/A&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;A href="ugg-matala-sandal-c-257.html"&gt;Ugg   Matala Sandal&lt;/A&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;A href="ugg-mayfaire-c-249.html"&gt;Ugg   Mayfaire&lt;/A&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href="ugg-napoule-sandal-c-258.html"&gt;Ugg   Napoule Sandal&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="STYLE2"&gt;&lt;A href="ugg-nightfall-c-246.html"&gt;Ugg   Nightfall&lt;/A&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;A href="ugg-skimmer-c-251.html"&gt;Ugg   Skimmer&lt;/A&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;A href="ugg-sundance-ii-c-245.html"&gt;Ugg   Sundance II&lt;/A&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;A href="ugg-ultimate-bind-c-247.html"&gt;Ugg   Ultimate Bind&lt;/A&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;A href="ugg-ultra-short-c-243.html"&gt;Ugg   Ultra Short&lt;/A&gt;&lt;/strong&gt;&lt;/p&gt;&lt;div class="commentPosted"&gt;Posted 07:38, 13 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment184"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment184"&gt;#184&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:uggsw" class="link-user" rel="internal"&gt;uggsw&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm184"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText184"&gt;&lt;p&gt;Timberland   Men Boots sale come in a stunning range of styles and colors in the   market.Online purchasing has become increasingly popular because &lt;a href=""&gt;&lt;strong&gt;Cheap Timberland Work Boots&lt;/strong&gt;&lt;/a&gt;  provides you   great convenience and you always can find the cheap timberland chukka boots   latest styles there. Plus timberland boots online are mostly sold at lower   prices than local stores,and you get to select from the wide range of   styles.Treat yourself to a pair of timberland classic boots today!Terrific &lt;a href=""title="Timberland Boots"&gt;&lt;strong&gt;Timberland Boots&lt;/strong&gt;&lt;/a&gt;. Absolutely impressed. This Timberland is a beautiful,   classically designed piece of work, with modern features. Donâ€™t miss this   chance!Today,Timberland Boots Sale have been a fashion trend.Be sure to choose &lt;a href=""title="Timberlands Shoes"&gt;&lt;strong&gt;Timberlands Shoes&lt;/strong&gt;&lt;/a&gt; that are made of high quality materials which just feel   very comfortable.I know that men put comfort and quality first.Thatâ€™s why&lt;a href=""title="Timberland Boots Sale"&gt;&lt;strong&gt; Timberland Boots Sale &lt;/strong&gt;&lt;/a&gt;have   committed to produce quality footwear.&lt;a href=""&gt;&lt;strong&gt;Timberland Work Boots&lt;/strong&gt;&lt;/a&gt; You need a pair of reliable foots for any   type of weather,including snowy or rainy days.These boots from &lt;strong&gt;&lt;a href=""title="Timberland Boots Online&lt;"&gt;Timberland Boots Online&lt;/a&gt;&lt;/strong&gt; are   made of premium waterproof leather and recycled rubber sole.The leather has a   gradient finish which makes them even more appealing,at least for men with a   sense of fashion.Timberland, In 2000,&lt;a href="timberland-mens-6-inch-boots-c-238.html"title="Men Timberland Boots"&gt;&lt;strong&gt;Men Timberland Boots&lt;/strong&gt;&lt;/a&gt; we have not only re-nominate the same year, the United   States, New Hampshire, published by business magazine â€œis located in New   Hampshireâ€™s popular list&lt;a href="timberland-mens-custom-boots-c-240.html"title="Timberland Men's Custom Boots "&gt;&lt;strong&gt;Timberland Men's Custom Boots &lt;/strong&gt;&lt;/a&gt; in, Timberland is on top. It is precisely because   there is such a good workplace environment, Timberland products are manufactured   in order to have reliable quality and long-beloved. If you are finding for Timberland   Boots for men,the our web site will be your best choice.People on the move will certainly emerge a pair of&lt;a href="timberland-mens-rolltop-boots-c-241.html"title="Timberland Men's Roll-Top Boots"&gt;&lt;strong&gt; Timberland Men's Roll-Top Boots&lt;/strong&gt;&lt;/a&gt;. But be careful, once you have experienced a positive   outdoor experience, &lt;a href="timberland-womens-6-inch-boots-c-242.html"title="Women Timberland Boots"&gt;&lt;strong&gt;Women Timberland Boots&lt;/strong&gt;&lt;/a&gt; you must not imagine being without it. We   know how to footwear comfort and timberland boot durability can only come from   expensive package. &lt;A href="timberland-womens-6-inch-boots-c-242.html"title="Timberland 6 Inch Boots"&gt;&lt;strong&gt;Timberland 6 Inch Boots&lt;/strong&gt;&lt;/A&gt; With timberlands reputation, the quality of their shoes, can   earn the average, especially expensive. However, this is definitely worth the   price of timberland boots to consider how to resist the normal wear and tear,   while providing you extreme comfort, you need to. Find timberland boots get   quality shoes if you want them to last.&lt;a href="www.officialtimberlands.com"&gt;&lt;strong&gt;www.officialtimberlands.com&lt;/strong&gt;&lt;/a&gt;&lt;BR&gt;
&lt;/p&gt;&lt;div class="commentPosted"&gt;Posted 07:44, 13 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment185"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment185"&gt;#185&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:vivianshea" class="link-user" rel="internal"&gt;vivianshea&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm185"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText185"&gt;Great and informative posting! &lt;a href=""&gt;Jobs in Brussels&lt;/a&gt;&lt;div class="commentPosted"&gt;Posted 13:39, 13 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment186"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment186"&gt;#186&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:chanelstory" class="link-user" rel="internal"&gt;chanelstory&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm186"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText186"&gt;&lt;a rel="dofollow"href=""&gt;Chanel bags&lt;/a&gt; is one of the most attractive brands in the world. &lt;a href="dofollow"http://www.chanelworlds.com/"&gt;Chanel Bags&lt;/a&gt; is not only a sign of taste and fashion, it is also a symbol of social status and recognition. &lt;a href="dofollow"http://www.chanelworlds.com/"&gt;ChanelWorlds.com&lt;/a&gt; is the best online store which provide&lt;a href="dofollow"http://www.chanelworlds.com/"&gt; Chanel Bags&lt;/a&gt;, &lt;a href="dofollow"http://www.chanelworlds.com/chanel-coco-bags-c-206.html"&gt;Chanel Coco&lt;/a&gt;, &lt;a href="dofollow"http://www.chanelworlds.com/chanel-purse-c-201.html"&gt;Chanel Purses&lt;/a&gt;, &lt;a href="dofollow"http://www.chanelworlds.com/chanel-sunglasses-c-196.html"&gt;Chanel   Sunglasses&lt;/a&gt; online, if you need some discount &lt;a href="dofollow"http://www.chanelworlds.com/"&gt;Chanel Handbags Online&lt;/a&gt;. You are able to select Cheap &lt;a href="dofollow"http://www.chanelworlds.com/"&gt;Chanel Bags&lt;/a&gt; from different modes, colors and materials on &lt;a href="dofollow"http://www.chanelworlds.com/"&gt;ChanelWorlds.com&lt;/a&gt;.We provide Highest Level  Quality,Attractive Price,Free Shipping Worldwide,Secure and Fast Delivery.&lt;div class="commentPosted"&gt;Posted 08:33, 15 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment187"&gt;&lt;div class="commentNum"&gt;&lt;a href="Tools_for_linked_data_from_DERI#comment187"&gt;#187&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;Tiffany jewelry&lt;a href="User:Tiffany_jewelry" class="new link-user" rel="internal"&gt;?&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm187"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText187"&gt;&lt;a href=""&gt;Tiffany jewelry&lt;/a&gt; manufacturers directory,cheap jewelry - lots of registered importers and exporters. &lt;a href=""&gt;Cheap tiffany jewelry&lt;/a&gt; manufacturers, Tiffany &amp;amp; co  jewelry suppliers, tiffany jewelry wholesales,
&lt;a href=""&gt;Tiffany Watches&lt;/a&gt;,exporters, sellers, traders and gold tiffany jewelry Distributors from China and around the world at www.goldtiffanyjewelry.com


&lt;a href=""&gt;Tiffany jewelry exporters&lt;/a&gt;,
&lt;a href="tiffany-accessories-c-25.html"&gt;Tiffany Accessories&lt;/a&gt;,
&lt;a href="tiffany-bangles-c-26.html"&gt;Tiffany Bangles&lt;/a&gt;,
&lt;a href="tiffany-bracelets-c-29.html"&gt;Tiffany Bracelet&lt;/a&gt;,
&lt;a href="tiffany-bracelets-new-c-31.html"&gt;Discont Tiffany Bracelet&lt;/a&gt;,
&lt;a href="tiffany-cufflinks-c-24.html"&gt;Discount Tiffany Cufflinks&lt;/a&gt;,
&lt;a href="tiffany-earrings-c-28.html"&gt;Fashion Tiffany Earring&lt;/a&gt;,
&lt;a href="tiffany-necklaces-c-30.html"&gt;Tiffany Necklaces&lt;/a&gt; ,
&lt;a href="tiffany-necklaces-new-c-32.html"&gt;Discount Tiffany Necklaces&lt;/a&gt;,
&lt;a href="tiffany-rings-c-27.html"&gt;Tiffany Rings&lt;/a&gt;,
&lt;a href="tiffany-watches-c-23.html"&gt;Tiffany Watches&lt;/a&gt;&lt;div class="commentPosted"&gt;Posted 07:50, 16 Aug 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="commentMore"&gt;Viewing 15 of 177 comments: &lt;a href="index.php?title=Tools_for_linked_data_from_DERI&amp;amp;commentcount=all#comments" onclick="return MTComments.GetComments('all');" id="commentViewAll"&gt;view all&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="commentForm"&gt;You must &lt;a href="index.php?title=Special:Userlogin&amp;amp;returntotitle=Tools+for+linked+data+from+DERI"&gt;login&lt;/a&gt; to post a comment.&lt;/div&gt;&lt;/div&gt;								
				&lt;div class="custom custom5"&gt;
									&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="bodyFooter"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;div class="Wik.is"&gt;&lt;div class="poweredBy"&gt;Powered by &lt;a href=""&gt; Wik.is Express: open source enterprise collaboration and wik software&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;
			&lt;div class="sourceforge" style="text-align: center; margin: 8px 0;"&gt;&lt;a href="http://wik.is/"&gt;&lt;img src="http://wik.is/wp-content/uploads/2015/06/logo1.png" alt=" Wik.is" /&gt;&lt;/a&gt;&lt;/div&gt; 		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;


&lt;script type="text/javascript"&gt;var _endtime = new Date().getTime(); var _size = 71998;&lt;/script&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuTools" style="display:none;"&gt;
	&lt;ul&gt;	&lt;li class="siteListRss"&gt;&lt;a href="Special:ListRss" title="RSS feeds"&gt;&lt;span&gt;&lt;/span&gt;RSS feeds&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteListusers"&gt;&lt;a href="User:" title="Users"&gt;&lt;span&gt;&lt;/span&gt;Users&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteListTemplates"&gt;&lt;a href="Template:" title="Templates"&gt;&lt;span&gt;&lt;/span&gt;Templates&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteSitemap"&gt;&lt;a href="Special:Sitemap" title="Sitemap"&gt;&lt;span&gt;&lt;/span&gt;Sitemap&lt;/a&gt;&lt;/li&gt;
	&lt;li class="sitePopularpages"&gt;&lt;a href="Special:Popularpages" title="Popular pages"&gt;&lt;span&gt;&lt;/span&gt;Popular pages&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteAbout"&gt;&lt;a href="Special:About" title="About"&gt;&lt;span&gt;&lt;/span&gt;About&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;	
&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuPageOptions" style="display:none;"&gt;
	&lt;ul&gt;	&lt;li class="pageEdit disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Edit page"&gt;&lt;span&gt;&lt;/span&gt;Edit page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageAdd disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');" title="New page"&gt;&lt;span&gt;&lt;/span&gt;New page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageRestrict disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Restrict access"&gt;&lt;span&gt;&lt;/span&gt;Restrict access&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageAttach disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Attach file"&gt;&lt;span&gt;&lt;/span&gt;Attach file&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageMove disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Move page"&gt;&lt;span&gt;&lt;/span&gt;Move page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageDelete disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Delete page"&gt;&lt;span&gt;&lt;/span&gt;Delete page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pagePrint "&gt;&lt;a href="index.php?title=Tools_for_linked_data_from_DERI&amp;amp;action=print" onclick="menuOff('menuPageOptions');return Print.open('/index.php?title=Tools_for_linked_data_from_DERI&amp;amp;action=print');" title="Print page"&gt;&lt;span&gt;&lt;/span&gt;Print page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageTags disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Tag"&gt;&lt;span&gt;&lt;/span&gt;Tag&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageEmail disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Email link"&gt;&lt;span&gt;&lt;/span&gt;Email link&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageProperties disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Set page properties"&gt;&lt;span&gt;&lt;/span&gt;Set page properties&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageTalk "&gt;&lt;a href="Talk:Tools_for_linked_data_from_DERI" onclick="menuOff('menuPageOptions');" title="Talk page"&gt;&lt;span&gt;&lt;/span&gt;Talk page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageWatch "&gt;&lt;a href="index.php?title=Tools_for_linked_data_from_DERI&amp;amp;action=watch" onclick="menuOff('menuPageOptions');" title="Watch page"&gt;&lt;span&gt;&lt;/span&gt;Watch page&lt;/a&gt;&lt;/li&gt;
&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuBacklink" style="display:none;"&gt;
	&lt;ul&gt;&lt;li class="first last"&gt;&lt;a href=""&gt;Federal Data Web 2.0 Wiki Pilot&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuPageContent" style="display:none;"&gt;
	&lt;div class="pageToc"&gt;&lt;h5&gt;Table of contents&lt;/h5&gt;&lt;em&gt;No headers&lt;/em&gt;&lt;/div&gt;&lt;/div&gt;


&lt;div class="ui-msg-wrap" id="MTMessage" style="display: none;"&gt;
	&lt;div class="ui-msg ui-errormsg" id="MTMessageStyle"&gt;
		&lt;div class="ui-msg-opt"&gt;
			&lt;ul&gt;
				&lt;li&gt;&lt;a href="#" class="dismiss" onclick="return MTMessage.Hide();"&gt;dismiss message&lt;/a&gt;&lt;/li&gt;
				&lt;li&gt;&lt;a href="#" class="details" id="MTMessageDetailsLink" onclick="return MTMessage.ShowDetails(this);"&gt;view details&lt;/a&gt;&lt;/li&gt;
			&lt;/ul&gt;
			&lt;div class="ui-msg-autoclose"&gt;
				&lt;span id="MTMessageUnpaused" style="display: inline;"&gt;Message will close by itself in &lt;span id="MTMessageTimer"&gt;&lt;/span&gt; seconds&lt;/span&gt;
				&lt;span id="MTMessagePaused" style="display: none;"&gt;Message timer has been stopped&lt;/span&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		&lt;div class="ui-msg-header" id="MTMessageHeader"&gt;&lt;/div&gt;
		&lt;div class="ui-msg-desc" id="MTMessageDesc"&gt;&lt;/div&gt;
		&lt;div class="ui-msg-desc" id="MTMessageDetails" style="display: none;"&gt;
			&lt;p&gt;Viewing Details:&lt;/p&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;&lt;div id="menuFiller"&gt;&lt;/div&gt;&lt;div id="bodyHeight"&gt;&lt;/div&gt;&lt;script src="urchin.js" type="text/javascript"&gt;&lt;/script&gt;
&lt;!-- Served by ip-10-250-75-15 in 0.29 secs. --&gt;
&lt;!-- /wik/site/settings: 0.061217784881592--&gt;
&lt;!-- /wik/users/=Anonymous: 0.028096914291382--&gt;
&lt;!-- /wik/site/services/1: 0.0071051120758057--&gt;
&lt;!-- /wik/pages/695/contents: 0.028494119644165--&gt;
&lt;!-- /wik/pages/695: 0.032377004623413--&gt;
&lt;!-- /wik/pages/695/comments: 0.021488904953003--&gt;
&lt;!-- /wik/pages/695/security: 0.0099649429321289--&gt;
&lt;!-- /wik/site/nav/=Tools%2Bfor%2Blinked%2Bdata%2Bfrom%2BDERI/full: 0.045743942260742--&gt;
&lt;!-- Total: 0.23448872566223--&gt;
&lt;!-- Real: 0.23448872566223--&gt;

&lt;/body&gt;
  
&lt;/html&gt;</text>
    <sha1>ce8375712bab2c718bb23926737d2ab85617ce94</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>UCoreSL</title>
  <ns>0</ns>
  <id>175</id>
  <revision>
    <id>396</id>
    <timestamp>2016-01-13T18:10:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;  &lt;html xmlns="..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="55040" xml:space="preserve">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;
 &lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us" dir=""&gt;
 &lt;head&gt;


    &lt;script type="text/javascript"&gt;var _starttime = new Date().getTime();&lt;/script&gt;
    &lt;meta http-equiv="Content-Type" content="text/html; charset=utf-8" /&gt;
    &lt;meta name="robots" content="index,follow" /&gt;
&lt;link rel="shortcut icon" href="favicon.ico" /&gt;
&lt;meta name="generator" content=" Wik.is" /&gt;
&lt;link rel="search" type="application/opensearchdescription+xml" title="Federal Data Web 2.0 Wiki Pilot Search" href="/@gui/opensearch/description" /&gt;    &lt;title&gt;Ucore-SL - Federal Data Web 2.0 Wiki Pilot&lt;/title&gt;
    
    &lt;!-- default css --&gt;
    &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/fiesta/_reset.css"/&gt;
    &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/common/css.php" /&gt; &lt;!--[if IE 7]&gt;&lt;style type="text/css"&gt;@import "/skins/common/_ie7.css";&lt;/style&gt;&lt;![endif]--&gt;&lt;!--[if IE 6]&gt;&lt;style type="text/css"&gt;@import "/skins/common/_ie.css";&lt;/style&gt;&lt;![endif]--&gt;    &lt;link rel="stylesheet" type="text/css" media="print" href="skins/common/print.css" /&gt;    
    &lt;!-- default scripting --&gt;
    &lt;script type="text/javascript" src="skins/common/js.php?perms=LOGIN,BROWSE,READ,SUBSCRIBE&amp;amp;lang=en-us"&gt;&lt;/script&gt;    
    &lt;!-- specific screen stylesheets--&gt;
        &lt;link rel="stylesheet" type="text/css" media="screen" href="skins/fiesta/sky-tangerine/css.php"/&gt;
        
    &lt;!-- specific print stylesheets --&gt;
    &lt;link rel="stylesheet" type="text/css" media="print" href="skins/fiesta/print.css" /&gt;
   
    &lt;!-- IE6 &amp; IE7 specific stuff --&gt;
    &lt;!--[if IE]&gt;&lt;meta http-equiv="imagetoolbar" content="no" /&gt;&lt;![endif]--&gt;
    &lt;!--[if IE 6]&gt;&lt;link rel="stylesheet" type="text/css" media="screen" href="/skins/fiesta/sky-tangerine/ie6.php"/&gt;&lt;![endif]--&gt;
    &lt;!--[if IE 7]&gt;&lt;link rel="stylesheet" type="text/css" media="screen" href="/skins/fiesta/sky-tangerine/ie7.php"/&gt;&lt;![endif]--&gt;
    
    	&lt;script type="text/javascript"&gt;

	    _page_redirect = false;
_path_tpl = '/skins/fiesta';
_path_skin = '/skins/fiesta/sky-tangerine';
_path_common = '/skins/common';
_path_icons = '/skins/common/icons';
editToken = '02d51ebce630aefc331ccc31af344b9e';
_userName = 'Anonymous';
_userId = '2';
var _editor_styles_path = ['/skins/fiesta/_editor.css', '/skins/fiesta/sky-tangerine/_content.css', ''];
_today = '17 Sep 2010';
baseHref = '/web/20100917133351/http://federaldata.Wik.is';
_page_titlePath = '/';
_page_titleName = 'Ucore-SL';
_page_ID = 1134;
_total_images = 6;
contextTopic = 'Ucore-SL';
_over_storage_quota = false;
saveFlag = false;

	    
		// remote scripting library
		// (c) copyright 2005 modernmethod, inc
		var sajax_debug_mode = false;
		var sajax_request_type = "POST";

		function sajax_debug(text) {
			if (sajax_debug_mode)
				alert("RSD: " + text);
		};

		function sajax_init_object() {
			sajax_debug("sajax_init_object() called..");

			var A = window.XMLHttpRequest ? new XMLHttpRequest() : window.ActiveXObject ? new ActiveXObject("Microsoft.XMLHTTP") : null;
			if (!A)
				sajax_debug("Could not create connection object.");
			return A;
		};
		function _sajax_do_call(x, func_name, args) {
			var i, x, n;
			var uri;
			var post_data;

			uri = "/index.php";
			if (sajax_request_type == "GET") {
				if (uri.indexOf("?") == -1) 
					uri = uri + "?rs=" + encodeURIComponent(func_name);
				else
					uri = uri + "&amp;rs=" + encodeURIComponent(func_name);
				for (i = 0; i &lt; args.length-1; i++) {
				    var a = args[i];
					uri = uri + "&amp;rsargs[]=" + encodeURIComponent(a);
				}
				uri = uri + "&amp;rsrnd=" + new Date().getTime();
				post_data = null;
			} else {
				post_data = "rs=" + func_name;
				for (i = 0; i &lt; args.length-1; i++) {
				    var a = args[i];
					post_data = post_data + "&amp;rsargs[]=" + encodeURIComponent(a);
				}
			}
			x.open(sajax_request_type, uri, true);
			if (sajax_request_type == "POST") {
				x.setRequestHeader("Method", "POST " + uri + " HTTP/1.1");
				x.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
			}
			x.onreadystatechange = function() {
				if (x.readyState != 4) 
					return;
				if (typeof sajax_debug != 'undefined') sajax_debug("received " + x.responseText);

				var status;
				var data = x.responseText.replace(/^\s+/, '');
				status = data.charAt(0);
				data = data.substring(2);
				if (status == "-") 
					alert("Error: " + data);
				else  
					args[args.length-1](data);
			}
			x.send(post_data);
			sajax_debug(func_name + " uri = " + uri + "/post = " + post_data);
			sajax_debug(func_name + " waiting..");
			return x;
		};
		function sajax_do_call(func_name, args) {
			x = sajax_init_object();
			_sajax_do_call(x, func_name, args);
			delete x;
		};

		function x_breadcrumbSet() { sajax_do_call("breadcrumbSet", x_breadcrumbSet.arguments); };
		function x_wfAdminUserForm() { sajax_do_call("wfAdminUserForm", x_wfAdminUserForm.arguments); };
		function x_wfSetUserOption() { sajax_do_call("wfSetUserOption", x_wfSetUserOption.arguments); };
		function x_wfSetRestrictions() { sajax_do_call("wfSetRestrictions", x_wfSetRestrictions.arguments); };
		function x_setUserOption() { sajax_do_call("setUserOption", x_setUserOption.arguments); };
		function x_wfValidateUserOrGroup() { sajax_do_call("wfValidateUserOrGroup", x_wfValidateUserOrGroup.arguments); };
		function x_wfSaveEdit() { sajax_do_call("wfSaveEdit", x_wfSaveEdit.arguments); };
		function x_wfQueryLinks() { sajax_do_call("wfQueryLinks", x_wfQueryLinks.arguments); };
		function x_loadInplaceEditor() { sajax_do_call("loadInplaceEditor", x_loadInplaceEditor.arguments); };
		function x_doSetbaseHref() { sajax_do_call("doSetbaseHref", x_doSetbaseHref.arguments); };
		function x_showFileAttachments() { sajax_do_call("showFileAttachments", x_showFileAttachments.arguments); };
		function x_doSectionEdit() { sajax_do_call("doSectionEdit", x_doSectionEdit.arguments); };
		function x_postComment() { sajax_do_call("postComment", x_postComment.arguments); };
		function x_getComments() { sajax_do_call("getComments", x_getComments.arguments); };
		function x_deleteComment() { sajax_do_call("deleteComment", x_deleteComment.arguments); };
		function x_editComment() { sajax_do_call("editComment", x_editComment.arguments); };
		function x_wfEmailPage() { sajax_do_call("wfEmailPage", x_wfEmailPage.arguments); };
		function x_wfCheckNewTitle() { sajax_do_call("wfCheckNewTitle", x_wfCheckNewTitle.arguments); };
		function x_wfDeleteFile() { sajax_do_call("wfDeleteFile", x_wfDeleteFile.arguments); };
		function x_wfSetPageProperties() { sajax_do_call("wfSetPageProperties", x_wfSetPageProperties.arguments); };
		function x_wfDeleteTopic() { sajax_do_call("wfDeleteTopic", x_wfDeleteTopic.arguments); };
		function x_wfRenameTopic() { sajax_do_call("wfRenameTopic", x_wfRenameTopic.arguments); };
		function x_wfMoveAttachments() { sajax_do_call("wfMoveAttachments", x_wfMoveAttachments.arguments); };
		function x_wfGetAttachmentUrl() { sajax_do_call("wfGetAttachmentUrl", x_wfGetAttachmentUrl.arguments); };
		function x_wfInlineImageGallery() { sajax_do_call("wfInlineImageGallery", x_wfInlineImageGallery.arguments); };
		function x_wfSetFileDescription() { sajax_do_call("wfSetFileDescription", x_wfSetFileDescription.arguments); };
		function x_wfChangeLoginView() { sajax_do_call("wfChangeLoginView", x_wfChangeLoginView.arguments); };
		function x_wfChangeLoginViewToCreate() { sajax_do_call("wfChangeLoginViewToCreate", x_wfChangeLoginViewToCreate.arguments); };
		function x_wfSaveCredsToSession() { sajax_do_call("wfSaveCredsToSession", x_wfSaveCredsToSession.arguments); };
		function x_wfChangeAddServiceView() { sajax_do_call("wfChangeAddServiceView", x_wfChangeAddServiceView.arguments); };
		function x_wfSaveLoginPageCreds() { sajax_do_call("wfSaveLoginPageCreds", x_wfSaveLoginPageCreds.arguments); };
		function x_wfRemindPassword() { sajax_do_call("wfRemindPassword", x_wfRemindPassword.arguments); };
		function x_wfChangeAvailUsersPage() { sajax_do_call("wfChangeAvailUsersPage", x_wfChangeAvailUsersPage.arguments); };
		
	    window.onbeforeunload = checkForChanges;

	    function checkForChanges() {
	        if (saveFlag &amp;&amp; !doCheckChanges(cur_editor)) {
	        	return "You have made changes to the content without saving your changes. Are you sure you want to exit this page?";
	        }
	    }
	    var aLt = new Array();aLt["attach-no-description"] = 'No description'; aLt["cancel"] = 'Cancel'; aLt["comment-delete"] = 'Are you sure you want to delete this comment?'; aLt["gallery-close"] = 'close'; aLt["gallery-next"] = 'next'; aLt["gallery-prev"] = 'prev'; aLt["internal-error"] = 'Sorry, but there was an internal problem - please try again soon.'; aLt["js-label_cancel"] = 'Cancel'; aLt["js-label_save"] = 'Save'; aLt["js-tooltip_cancel"] = 'Exit Without Saving Changes'; aLt["js-tooltip_save"] = 'Save and Exit (Alt+S)'; aLt["ldap-provide-credentials"] = 'Please provide external service login credentials.'; aLt["loading"] = 'Loading...'; aLt["menu-confirm-delete"] = 'Are you sure you want to delete this file?'; aLt["menu-delete-file"] = 'Delete'; aLt["menu-edit-description"] = 'Edit description'; aLt["menu-move-file"] = 'Move'; aLt["menu-previous-versions"] = 'Previous versions'; aLt["menu-view-original"] = 'View original'; aLt["print-end-notes"] = 'Endnotes'; aLt["ready"] = 'Ready'; aLt["submit"] = 'Submit'; aLt["select-files"] = 'Select files...'; aLt["wikibits-attach-another"] = 'Attach another file'; aLt["wikibits-attach-file"] = 'Attach File'; aLt["wikibits-cant-attach-editing"] = 'Sorry, you can\'t attach files while editing a page. Please close the editor first.'; aLt["wikibits-edit-section"] = 'Edit section'; aLt["wikibits-remove-file"] = 'Remove file';  var wfMsg = function (key) { return aLt[key] ? aLt[key] : 'MISSING: ' + key; };var navMaxWidth = 1600;
	//hook in menu clicking events to the document's body
	YAHOO.util.Event.addListener(document, "click", function () { FileMenu.bodyClick(); DWMenu.BodyClick(); });	
	YAHOO.util.Event.onDOMReady(function () { new clientWindow }); 
	
                
		YAHOO.util.Event.onAvailable("siteNavTree", wik.nav.init, wik.nav, true);
		
	
			YAHOO.util.Event.onDOMReady(function() {
			tb_init('a.lightbox, area.lightbox, input.lightbox, a[@rel=awesomebox]');//pass where to apply thickbox
			imgLoader = new Image();// preload image
			imgLoader.src = tb_pathToImage;
		});
		
		YAHOO.util.Event.onDOMReady(function() { 
			MTComments.HookBehavior();
		});
		&lt;/script&gt;
	
	&lt;!-- styles overwritten via control panel - load this css last --&gt;	
	 
&lt;/head&gt;

&lt;body class="  en-us"&gt;


&lt;noscript&gt;This application requires Javascript to be enabled.&lt;/noscript&gt;

&lt;div class="global"&gt;
	&lt;div class="globalWrap"&gt;
		&lt;div class="header"&gt;
		
			&lt;div class="mastPre"&gt;&lt;/div&gt;
			&lt;div class="mast"&gt;
				
				&lt;div class="siteLogo"&gt;
					&lt;a href="" title="Federal Data Web 2.0 Wiki Pilot"&gt;&lt;img src="skins/fiesta/sky-tangerine/logo.png" alt="Federal Data Web 2.0 Wiki Pilot" title="Federal Data Web 2.0 Wiki Pilot"/&gt;&lt;/a&gt;		
				&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="mastPost"&gt;&lt;/div&gt;
			
			&lt;div class="siteNavPre"&gt;&lt;/div&gt;
			&lt;div class="siteNav"&gt;
				&lt;div class="userAuthPre"&gt;&lt;/div&gt;
							&lt;div class="userAuth"&gt;
			&lt;span&gt;Logged in:&lt;/span&gt;			&lt;span&gt;Logged in as:&lt;/span&gt;					
	 		&lt;a href="index.php?title=Special:Userlogin&amp;amp;returntotitle=Ucore-SL" class="userLogin"&gt;Log in&lt;/a&gt;		&lt;/div&gt;
						
									&lt;div class="userAuthPost"&gt;&lt;/div&gt;
				
				&lt;div class="custom custom2"&gt;
									&lt;/div&gt;
				
					
				&lt;div class="navPre"&gt;&lt;/div&gt;
					&lt;div id="siteNavTree"&gt;&lt;div class="node dockedNode homeNode lastDocked parentClosed" id="n21" c="n2348,n710,n70,n542,n497,n1144,n702,n2349,n1437,n2346,n990,n35,n33,n34,n526,n543,n1884,n46,n842,n498,n418,n75,n73,n654,n1883,n534,n704,n661,n653,n711,n1473,n2352,n427,n1140,n2287,n581,n695,n1935,n1134,n500,n1757" path=""&gt;&lt;a href="" title="Federal Data Web 2.0 Wiki Pilot"&gt;&lt;span&gt;Federal Data Web 2....&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling moreNodes" id="n2348" p="n21" path="Analytics/" content="Analytics" contentTitle="Analytics" hiddenNodes="n710,n70,n542,n497,n1144,n702,n2349,n1437,n2346,n990,n35,n33,n34,n526,n543"&gt;&lt;a href="Analytics" title="More..."&gt;&lt;span class="more"&gt;...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n710" p="n21" path="Blackbook_2_and_3/"&gt;&lt;a href="Blackbook_2_and_3" title="Blackbook 2 and 3"&gt;&lt;span&gt;Blackbook 2 and 3&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n70" p="n21" path="Blog_(Web_Log)/"&gt;&lt;a href="Blog_(Web_Log)" title="Blog (Web Log)"&gt;&lt;span&gt;Blog (Web Log)&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n542" p="n21" path="Cambridge_Semantics_Recovery.gov/"&gt;&lt;a href="Cambridge_Semantics_Recovery.gov" title="Cambridge Semantics Recovery.gov"&gt;&lt;span&gt;Cambridge Semantic...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n497" p="n21" path="Comments_and_Innovations_for_the_Open_Government_and_Transparency_Directive/"&gt;&lt;a href="Comments_and_Innovations_for_the_Open_Government_and_Transparency_Directive" title="Comments and Innovations for the Open Government and Transparency Directive"&gt;&lt;span&gt;Comments and Innov...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1144" p="n21" path="Data.gov/"&gt;&lt;a href="Data.gov" title="Data.gov Adds Geoviewer"&gt;&lt;span&gt;Data.gov Adds Geovi...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n702" p="n21" path="Data.gov_Concept_of_Operations_v0.7/"&gt;&lt;a href="Data.gov_Concept_of_Operations_v0.7" title="Data.gov Concept of Operations"&gt;&lt;span&gt;Data.gov Concept of...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n2349" p="n21" path="Data.gov_CONOPS/"&gt;&lt;a href="Data.gov_CONOPS" title="Data.gov CONOPS"&gt;&lt;span&gt;Data.gov CONOPS&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n1437" p="n21" path="Data.gov%2fsemantic/"&gt;&lt;a href="Data.gov%2f%2fsemantic" title="Data.gov/semantic"&gt;&lt;span&gt;Data.gov/semantic&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n2346" p="n21" path="Data_Science/" cd="0"&gt;&lt;a href="Data_Science" title="Data Science"&gt;&lt;span&gt;Data Science&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n990" p="n21" path="Executive_Office_of_the_President_-_OMB_and_NSA_Detail/"&gt;&lt;a href="Executive_Office_of_the_President_-_OMB_and_NSA_Detail" title="Executive Office of the President - OMB and NSA Detail for Data.gov"&gt;&lt;span&gt;Executive Office of ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n35" p="n21" path="Federal_Data_Architecture_Subcommittee_(DAS)/" cd="0"&gt;&lt;a href="Federal_Data_Architecture_Subcommittee_(DAS)" title="Federal Data Architecture Subcommittee (DAS)"&gt;&lt;span&gt;Federal Data Archite...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling closedNode hiddenNode" id="n33" p="n21" path="Federal_Data_Reference_Model/"&gt;&lt;a href="Federal_Data_Reference_Model" title="Federal Data Reference Model"&gt;&lt;span&gt;Federal Data Refere...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n34" p="n21" path="Federal_Data_Reference_Model_2.0/" cd="0"&gt;&lt;a href="Federal_Data_Reference_Model_2.0" title="Federal Data Reference Model 2.0"&gt;&lt;span&gt;Federal Data Refere...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n526" p="n21" path="Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form/" cd="0"&gt;&lt;a href="Federal_Enterprise_Architecture_Reference_Model_Revision_Submission_Form" title="Federal Enterprise Architecture Reference Model Revision Submission Form (DRM 3.0)"&gt;&lt;span&gt;Federal Enterprise A...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed closedNode hiddenNode" id="n543" p="n21" path="Federal_Enterprise_Architecture_Security_and_Privacy_Profile_Version_3.0/" cd="0"&gt;&lt;a href="Federal_Enterprise_Architecture_Security_and_Privacy_Profile_Version_3.0" title="Federal Enterprise Architecture Security and Privacy Profile Version 3.0"&gt;&lt;span&gt;Federal Enterprise A...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1884" p="n21" path="Federal_IT_Dashboard/"&gt;&lt;a href="Federal_IT_Dashboard" title="Federal IT Dashboard"&gt;&lt;span&gt;Federal IT Dashboar...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n46" p="n21" path="Federal_Semantic_Interoperability_Community_of_Practice_(SICoP)/" cd="0"&gt;&lt;a href="Federal_Semantic_Interoperability_Community_of_Practice_(SICoP)" title="Federal Semantic Interoperability Community of Practice (SICoP)"&gt;&lt;span&gt;Federal Semantic Int...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n842" p="n21" path="FGDC_Standards_WG_meeting_-_February_23,_2010/"&gt;&lt;a href="FGDC_Standards_WG_meeting_-_February_23%2c_2010" title="FGDC Standards WG Meeting - February 23, 2010"&gt;&lt;span&gt;FGDC Standards WG ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n498" p="n21" path="George_Thomas_on_Recovery.gov/"&gt;&lt;a href="George_Thomas_on_Recovery.gov" title="George Thomas on Recovery.gov"&gt;&lt;span&gt;George Thomas on R...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n418" p="n21" path="Harnessing_the_Power_of_Digital_Data_for_Science_and_Society/" cd="0"&gt;&lt;a href="Harnessing_the_Power_of_Digital_Data_for_Science_and_Society" title="Harnessing the Power of Digital Data for Science and Society"&gt;&lt;span&gt;Harnessing the Powe...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n75" p="n21" path="Interagency_Forum_on_Data_Preservation,_Stewardship,_and_LifeCycle_ESIP_Federation_Meeting,_January_8,_2009/"&gt;&lt;a href="Interagency_Forum_on_Data_Preservation%2c_Stewardship%2c_and_LifeCycle_ESIP_Federation_Meeting%2c_January_8%2c_2009" title="Interagency Forum on Data Preservation, Stewardship, and LifeCycle ESIP Federation Meeting, January 8, 2009"&gt;&lt;span&gt;Interagency Forum o...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n73" p="n21" path="Interagency_Working_Group_on_Digitial_Data/" cd="0"&gt;&lt;a href="Interagency_Working_Group_on_Digitial_Data" title="Interagency Working Group on Digitial Data"&gt;&lt;span&gt;Interagency Working...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n654" p="n21" path="June_4,_2009_How_Does_Government_Become_an_Open_Platform?/"&gt;&lt;a href="June_4%2c_2009_How_Does_Government_Become_an_Open_Platform%3f" title="June 4, 2009 How Does Government Become an Open Platform?"&gt;&lt;span&gt;June 4, 2009 How Do...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1883" p="n21" path="Labor's_Enforcement_Data_Catalog/"&gt;&lt;a href="Labor's_Enforcement_Data_Catalog" title="Labor's Enforcement Data Catalog"&gt;&lt;span&gt;Labor's Enforcement...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n534" p="n21" path="May_13,_2009_Semantic_Web_Meetup/"&gt;&lt;a href="May_13%2c_2009_Semantic_Web_Meetup" title="May 13, 2009 Semantic Web Meetup"&gt;&lt;span&gt;May 13, 2009 Seman...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n704" p="n21" path="NIEM/"&gt;&lt;a href="NIEM" title="NIEM"&gt;&lt;span&gt;NIEM&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n661" p="n21" path="Open_Group_Enterprise_Vocabularly_Workshop_June_3,_2009/"&gt;&lt;a href="Open_Group_Enterprise_Vocabularly_Workshop_June_3%2c_2009" title="Open Group Enterprise Vocabularly Workshop June 3, 2009"&gt;&lt;span&gt;Open Group Enterpri...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n653" p="n21" path="Open_Group_Enterprise_Vocabulary_Workshop_May_20,_2009/"&gt;&lt;a href="Open_Group_Enterprise_Vocabulary_Workshop_May_20%2c_2009" title="Open Group Enterprise Vocabulary Workshop May 20, 2009"&gt;&lt;span&gt;Open Group Enterpri...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n711" p="n21" path="Page_Title/"&gt;&lt;a href="Page_Title" title="Open Government Directive Workshop, January 11, 2010"&gt;&lt;span&gt;Open Government Di...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1473" p="n21" path="Scientific_Data_Management_for_Government_Agencies/"&gt;&lt;a href="Scientific_Data_Management_for_Government_Agencies" title="Scientific Data Management for Government Agencies"&gt;&lt;span&gt;Scientific Data Mana...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n2352" p="n21" path="Semantic_eScience/" cd="0"&gt;&lt;a href="Semantic_eScience" title="Semantic eScience"&gt;&lt;span&gt;Semantic eScience&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n427" p="n21" path="Statistical_Abstract_of_the_United_States:_2009/" cd="0"&gt;&lt;a href="Statistical_Abstract_of_the_United_States%3a_2009" title="Statistical Abstract of the United States: 2009"&gt;&lt;span&gt;Statistical Abstract ...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n1140" p="n21" path="Statistics/" cd="0"&gt;&lt;a href="Statistics" title="Statistics"&gt;&lt;span&gt;Statistics&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n2287" p="n21" path="Survey_of_EPA_and_Other_Federal_Agency_Scientific_Data_Management_Policies_and_Guidance_2010/" cd="0"&gt;&lt;a href="Survey_of_EPA_and_Other_Federal_Agency_Scientific_Data_Management_Policies_and_Guidance_2010" title="Survey of EPA and Other Federal Agency Scientific Data Management Policies and Guidance 2010"&gt;&lt;span&gt;Survey of EPA and O...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n581" p="n21" path="The_Recovery_Dialogue_on_IT_Solutions/" cd="0"&gt;&lt;a href="The_Recovery_Dialogue_on_IT_Solutions" title="The Recovery Dialogue on IT Solutions"&gt;&lt;span&gt;The Recovery Dialog...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n695" p="n21" path="Tools_for_linked_data_from_DERI/"&gt;&lt;a href="Tools_for_linked_data_from_DERI" title="Tools for linked data from DERI"&gt;&lt;span&gt;Tools for linked dat...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1935" p="n21" path="Top_Secret_America/"&gt;&lt;a href="Top_Secret_America" title="Top Secret America"&gt;&lt;span&gt;Top Secret America&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentOpen selected" id="n1134" c="n1135" p="n21" path="Ucore-SL/"&gt;&lt;a href="Ucore-SL" title="Ucore-SL"&gt;&lt;span&gt;Ucore-SL&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode selectedChild" id="n1135" p="n1134" path="Ucore-SL/Universal_Core_Semantic_Layer/"&gt;&lt;a href="Ucore-SL/Universal_Core_Semantic_Layer" title="Universal Core Semantic Layer"&gt;&lt;span&gt;Universal Core Sema...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling parentClosed" id="n500" p="n21" path="W3C_eGovernment_Interest_Group/" cd="0"&gt;&lt;a href="W3C_eGovernment_Interest_Group" title="W3C eGovernment Interest Group"&gt;&lt;span&gt;W3C eGovernment In...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="node childNode sibling" id="n1757" p="n21" path="White_House_Salaries/"&gt;&lt;a href="White_House_Salaries" title="White House Salaries"&gt;&lt;span&gt;White House Salarie...&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;				&lt;div class="navPost"&gt;&lt;/div&gt;
					
				&lt;div class="custom"&gt;
									&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="siteNavPost"&gt;&lt;/div&gt;
		&lt;/div&gt;
				
		&lt;div class="body"&gt;
			&lt;div class="bodyHeader"&gt;
				&lt;div class="pre"&gt;&lt;/div&gt;
				&lt;div class="post"&gt;&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="page"&gt;
				&lt;!-- required print options --&gt;
								
				&lt;div class="custom custom1"&gt;
								&lt;/div&gt;
				
				&lt;div class="siteNav"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
						
	&lt;div class="siteSearch"&gt;
		&lt;fieldset class="search"&gt;
	 		&lt;form action="Special:Search"&gt;
		        &lt;span&gt;Search: &lt;/span&gt;&lt;input id="searchInput" class="inputText" name="search" type="text" value="" /&gt;
				&lt;input type="hidden" name="type" value="fulltext" /&gt;
		        &lt;input type="submit" name="go" class="inputSubmit" value="Find" /&gt;
			&lt;/form&gt;
		&lt;/fieldset&gt;
	&lt;/div&gt;
					
					&lt;ul&gt;
						&lt;li class="userPage"&gt;&lt;a href="User:Anonymous"&gt;&lt;span&gt;&lt;/span&gt;My Page&lt;/a&gt;&lt;/li&gt;
												&lt;li class="siteChanges"&gt;&lt;a href="Special:Recentchanges"&gt;&lt;span&gt;&lt;/span&gt;Recent changes&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteTools"&gt;&lt;a href="#" onclick="return DWMenu.Position('menuTools', this, 0, 0);"&gt;&lt;span&gt;&lt;/span&gt;Tools&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteHelp"&gt;&lt;a href="Resources/Documentation/FAQ/MindTouch_Express"&gt;&lt;span&gt;&lt;/span&gt;Help&lt;/a&gt;&lt;/li&gt;
						&lt;li class="siteHelp"&gt;&lt;a href="pro/"&gt;&lt;span&gt;&lt;/span&gt;Go Pro&lt;/a&gt;&lt;/li&gt;					&lt;/ul&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="pageBar"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
					&lt;div class="pageRevision"&gt;
						&lt;!-- last modified --&gt;
						Page last modified &lt;a href="index.php?title=Ucore-SL&amp;amp;action=history" title="16:42, 6 Sep 2010"&gt;16:42, 6 Sep 2010&lt;/a&gt; by &lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;						&lt;!-- end last modified --&gt;					
					&lt;/div&gt;
					&lt;div class="pageNav"&gt;
						&lt;ul&gt;
							&lt;li class="pageEdit"&gt;&lt;a href="#" title="Edit page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Edit page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageAdd"&gt;&lt;a href="#" title="New page" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;New page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageRestrict"&gt;&lt;a href="#" title="Restrict access" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Restrict access&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageAttach"&gt;&lt;a href="#" title="Attach file" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Attach file&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageMove"&gt;&lt;a href="#" title="Move page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Move page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageDelete"&gt;&lt;a href="#" title="Delete page" onclick="return false" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Delete page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pagePrint"&gt;&lt;a href="index.php?title=Ucore-SL&amp;amp;action=print" title="Print page" onclick="return Print.open('/index.php?title=Ucore-SL&amp;amp;action=print');" class=""&gt;&lt;span&gt;&lt;/span&gt;Print page&lt;/a&gt;&lt;/li&gt;
							&lt;li class="pageMore"&gt;&lt;a href="#" onclick="return DWMenu.Position('menuPageOptions', this, 0, 0);"&gt;&lt;span&gt;&lt;/span&gt;More&lt;/a&gt;&lt;/li&gt;
							&lt;li class="navSplit"&gt;&lt;/li&gt;
							&lt;li class="pageToc"&gt;&lt;a href="#" title="Table of contents" onclick="return DWMenu.Position('menuPageContent', this, -2, 0)" class="disabled"&gt;&lt;span&gt;&lt;/span&gt;Table of contents&lt;/a&gt;&lt;/li&gt;
						&lt;/ul&gt;
					&lt;/div&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="pageContentFrame"&gt;
				&lt;div class="custom custom4"&gt;
								&lt;/div&gt;
				
				&lt;div id="pageContent" class="pageContent"&gt;
							 				&lt;div class="hierarchy"&gt;
		 					&lt;span class="dw-hierarchy"&gt;&lt;a href=""&gt;Federal Data Web 2.0 Wiki Pilot&lt;/a&gt; &amp;gt; Ucore-SL&lt;/span&gt;		 				&lt;/div&gt;
	 								
										&lt;div class="pageTitle"&gt;
												&lt;h1 id="title"&gt;&lt;span  class="pageRestricted" &gt;Ucore-SL&lt;/span&gt;&lt;/h1&gt;
					&lt;/div&gt;
					
								
					&lt;div class="pageStatus"&gt;
 					     					&lt;/div&gt;
 					
 							
					&lt;div class="PageDW-UcoreSL"&gt;								
	 				&lt;div id="page-top"&gt;&lt;div id="pageToc"&gt;&lt;div class="pageToc"&gt;&lt;h5&gt;Table of contents&lt;/h5&gt;&lt;em&gt;No headers&lt;/em&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="pageText" id="pageText"&gt; &lt;p&gt;UCore is an acronym for Universal Core, a U.S. government project to facilitate sharing of data across U.S. government systems. Source: &lt;a class="external" title="http://en.wikipedia.org/wiki/UCore" rel="external nofollow" target="_blank" href="wiki/UCore"&gt;Wikipedia&lt;/a&gt;&amp;nbsp;&amp;nbsp;Also see the official UCORE &lt;a class="link-https" title="https://ucore.gov/" rel="external nofollow" target="_blank" href=""&gt;Web site&lt;/a&gt;&amp;nbsp;.&lt;/p&gt; &lt;p&gt;Please Register for the Wiki and send an email to &lt;a rel="freelink" href="mailto:bniemann@cox.net" class=" link-mailto"&gt;bniemann@cox.net&lt;/a&gt; to request authoring rights for this wiki page.&lt;/p&gt; &lt;p&gt;To contact someone regarding UCore-SL, email &lt;a class=" link-mailto" rel="external nofollow" target="_blank" href="mailto:james.schoening@us.army.mil" title="mailto:james.schoening@us.army.mil"&gt;james.schoening@us.army.mil&lt;/a&gt; or call him at 732 532 6820. &lt;/p&gt; &lt;p&gt;&lt;a class="internal" rel="internal" href="Ucore-SL/Universal_Core_Semantic_Layer"&gt;Universal Core Semantic Layer&amp;nbsp;&lt;/a&gt;&lt;/p&gt; &lt;p&gt;Spotfire &lt;a rel="internal" href="@api/wik/files/1562/=NIEMandUCORE2SemanticLayer.dxp" class="iconitext-16 ext-dxp internal"&gt;File&lt;/a&gt;, &lt;a title="http://registration.spotfire.com/eval/default.asp?source=home&amp;amp;utm_source=home&amp;amp;utm_medium=button&amp;amp;utm_campaign=Try%2Bit" class="external" rel="external nofollow" target="_blank" href="eval/default.asp?source=home&amp;amp;utm_source=home&amp;amp;utm_medium=button&amp;amp;utm_campaign=Try%2Bit"&gt;Free Trial Client&lt;/a&gt;, &lt;a title="http://goto.spotfire.com/g/?P5GKGVDIQF=clicksrc:home" class="external" rel="external nofollow" target="_blank" href="g/?P5GKGVDIQF=clicksrc:home"&gt;Free Silver&lt;/a&gt; and, &lt;a title="http://ondemand.spotfire.com/public/ViewAnalysis.aspx?file=/Users/FAMIEVL-91915/Public/NIEMandUCORE2SemanticLayer.dxp&amp;amp;waid=b369a6093bed8ae6231e2-ad7b" class="external" rel="external nofollow" target="_blank" href="public/ViewAnalysis.aspx?file=/Users/FAMIEVL-91915/Public/NIEMandUCORE2SemanticLayer.dxp&amp;amp;waid=b369a6093bed8ae6231e2-ad7b"&gt;Web Player&lt;/a&gt; &lt;/p&gt; &lt;p&gt;&lt;object data="http://ondemand.spotfire.com/public/ViewAnalysis.aspx?file=/Users/FAMIEVL-91915/Public/NIEMandUCORE2SemanticLayer.dxp&amp;amp;waid=c051aebd1efb2d8940048-ad7b%22" width="750" height="800"&gt; &lt;embed src="/web/20100917133351oe_/http://ondemand.spotfire.com/public/ViewAnalysis.aspx?file=/Users/FAMIEVL-91915/Public/NIEMandUCORE2SemanticLayer.dxp&amp;amp;waid=c051aebd1efb2d8940048-ad7b" width="750" height="800"&gt;&lt;/embed&gt; Error: Embedded data could not be displayed. Use Google Chrome&lt;/object&gt; &lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="printfooter" id="printfooter"&gt;&lt;hr /&gt;
&lt;p&gt;Retrieved from "&lt;a href="Ucore-SL"&gt;http://federaldata.Wik.is/Ucore-SL&lt;/a&gt;"&lt;/p&gt;
&lt;/div&gt;
	 				&lt;/div&gt;
				&lt;/div&gt;
				&lt;/div&gt;
				&lt;div class="DW-clear"&gt;&lt;/div&gt;
								&lt;div class="pageInfo"&gt;
					&lt;dl&gt;
						&lt;dt class="pageTags"&gt;&lt;span&gt;&lt;/span&gt;Tag page&lt;/dt&gt;
						&lt;dd class="pageTags"&gt;
			 				&lt;div id="pageTags"&gt;&lt;div class="pageTagList"&gt;&lt;div class="item taglist"&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;		 				&lt;/dd&gt;
						
						&lt;dt class="pageIncomingLinks"&gt;&lt;span&gt;&lt;/span&gt;What links here&lt;/dt&gt;
						&lt;dd class="pageIncomingLinks"&gt;&lt;/dd&gt;
					&lt;/dl&gt;
				&lt;/div&gt;
				
								
				&lt;div class="file"&gt;
					&lt;h2&gt;Files 13&lt;/h2&gt;
					&lt;div class="fileAdd"&gt;
						&lt;a href="Ucore-SL" class="disabled" onclick="return false"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="attach" alt="" /&gt;&lt;/span&gt;&lt;span class="text"&gt;Attach file or image&lt;/span&gt;&lt;/a&gt;					&lt;/div&gt;
					&lt;div class="fileList"&gt;
		 				&lt;div id="pageFiles"&gt;&lt;div class="filescontent" id="attachFiles"&gt;&lt;div class="table" id="attachTable"&gt;&lt;table class="table" width="100%" cellspacing="0" cellpadding="0" border="0"&gt;&lt;colgroup&gt;&lt;col width="16"&gt;&lt;/col&gt;&lt;col width="16"&gt;&lt;/col&gt;&lt;col width=""&gt;&lt;/col&gt;&lt;col width="80"&gt;&lt;/col&gt;&lt;col width="145"&gt;&lt;/col&gt;&lt;col width="115"&gt;&lt;/col&gt;&lt;col width="75"&gt;&lt;/col&gt;&lt;/colgroup&gt;&lt;tbody&gt;&lt;tr class="bg1"&gt;&lt;th class="col1" colspan="3"&gt;File&lt;/th&gt;&lt;th class="col4"&gt;Size&lt;/th&gt;&lt;th class="col5"&gt;Date&lt;/th&gt;&lt;th class="col6"&gt;Attached by&lt;/th&gt;&lt;th class="col7"&gt;&amp;nbsp;&lt;/th&gt;&lt;/tr&gt;&lt;tr class="bg1"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/468/=C2_Core_Brief_NATO_Oct2009_ver6.ppt" class="filelink" title="C2_Core_Brief_NATO_Oct2009_ver6.ppt"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-ppt" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/468/=C2_Core_Brief_NATO_Oct2009_ver6.ppt" class="filelink" title="C2_Core_Brief_NATO_Oct2009_ver6.ppt"&gt;C2_Core_Brief_NATO_Oct2009_ver6.ppt&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_27d6f6fef1f643663ab4c79d7927259b"&gt;&lt;span class="desctext" id="fileDescDisplay_468"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;3.68 MB&lt;/td&gt;&lt;td class="col5"&gt;14:53, 22 Apr 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, '27d6f6fef1f643663ab4c79d7927259b', '468', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg2 groupparent"&gt;&lt;td class="col1"&gt;&lt;a href="#" onclick="return toggleAttachments('1564')" class="internal"&gt;&lt;span id="showlink-1564" style="display:none;"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="expand" alt="" /&gt;&lt;/span&gt;&lt;/span&gt;&lt;span id="hidelink-1564"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="contract" alt="" /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/1564/=niem-2.1.xls" class="filelink" title="niem-2.1.xls"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-xls" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/1564/=niem-2.1.xls" class="filelink" title="niem-2.1.xls"&gt;niem-2.1.xls&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_1582d9166946ddd5204a2377c0b07e54"&gt;&lt;span class="desctext" id="fileDescDisplay_1564"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;6.64 MB&lt;/td&gt;&lt;td class="col5"&gt;02:31, 13 Sep 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, '1582d9166946ddd5204a2377c0b07e54', '1564', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="attach_1564 bg2 group" style="display: none"&gt;&lt;td class="col1"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="dotcontinue" alt="" /&gt;&lt;/span&gt;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/1564/=niem-2.1.xls?revision=1" class="filelink" title="niem-2.1.xls"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-xls" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/1564/=niem-2.1.xls?revision=1" class="filelink" title="niem-2.1.xls"&gt;niem-2.1.xls&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_1582d9166946ddd5204a2377c0b07e54"&gt;&lt;span class="desctext" id="fileDescDisplay_1564"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;6.06 MB&lt;/td&gt;&lt;td class="col5"&gt;14:17, 15 Aug 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg1"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/1563/=niem-2.1-developers.xls" class="filelink" title="niem-2.1-developers.xls"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-xls" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/1563/=niem-2.1-developers.xls" class="filelink" title="niem-2.1-developers.xls"&gt;niem-2.1-developers.xls&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_471a14785d1d5c9f8295e09547b33d49"&gt;&lt;span class="desctext" id="fileDescDisplay_1563"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;9.71 MB&lt;/td&gt;&lt;td class="col5"&gt;14:17, 15 Aug 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, '471a14785d1d5c9f8295e09547b33d49', '1563', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg2 groupparent"&gt;&lt;td class="col1"&gt;&lt;a href="#" onclick="return toggleAttachments('1562')" class="internal"&gt;&lt;span id="showlink-1562" style="display:none;"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="expand" alt="" /&gt;&lt;/span&gt;&lt;/span&gt;&lt;span id="hidelink-1562"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="contract" alt="" /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/1562/=NIEMandUCORE2SemanticLayer.dxp" class="filelink" title="NIEMandUCORE2SemanticLayer.dxp"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-unknown" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/1562/=NIEMandUCORE2SemanticLayer.dxp" class="filelink" title="NIEMandUCORE2SemanticLayer.dxp"&gt;NIEMandUCORE2SemanticLayer.dxp&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_8af0f3ea475d4d74da9a6aab6d7279dd"&gt;&lt;span class="desctext" id="fileDescDisplay_1562"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;2.88 MB&lt;/td&gt;&lt;td class="col5"&gt;20:25, 22 Aug 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, '8af0f3ea475d4d74da9a6aab6d7279dd', '1562', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="attach_1562 bg2 group" style="display: none"&gt;&lt;td class="col1"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="dotcontinue" alt="" /&gt;&lt;/span&gt;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/1562/=NIEMandUCORE2SemanticLayer.dxp?revision=1" class="filelink" title="NIEMandUCORE2SemanticLayer.dxp"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-unknown" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/1562/=NIEMandUCORE2SemanticLayer.dxp?revision=1" class="filelink" title="NIEMandUCORE2SemanticLayer.dxp"&gt;NIEMandUCORE2SemanticLayer.dxp&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_8af0f3ea475d4d74da9a6aab6d7279dd"&gt;&lt;span class="desctext" id="fileDescDisplay_1562"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;2.73 MB&lt;/td&gt;&lt;td class="col5"&gt;14:17, 15 Aug 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg1"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/180/=SmithOIC2009_Final.pdf" class="filelink" title="SmithOIC2009 Final.pdf"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-pdf" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/180/=SmithOIC2009_Final.pdf" class="filelink" title="SmithOIC2009 Final.pdf"&gt;SmithOIC2009 Final.pdf&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_4e11adf4526ab1c104a6ceb76cb894c6"&gt;&lt;span class="desctext" id="fileDescDisplay_180"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;91 kB&lt;/td&gt;&lt;td class="col5"&gt;09:47, 17 Apr 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, '4e11adf4526ab1c104a6ceb76cb894c6', '180', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg2"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/181/=UCore-SL_File_Descriptions.xls" class="filelink" title="UCore-SL File Descriptions.xls"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-xls" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/181/=UCore-SL_File_Descriptions.xls" class="filelink" title="UCore-SL File Descriptions.xls"&gt;UCore-SL File Descriptions.xls&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_64248c0c4ede45164f029d44316437fb"&gt;&lt;span class="desctext" id="fileDescDisplay_181"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;20.5 kB&lt;/td&gt;&lt;td class="col5"&gt;09:47, 17 Apr 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, '64248c0c4ede45164f029d44316437fb', '181', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg1"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/182/=UCore-SL_Axioms_1.0_08-28-2009.xlsx" class="filelink" title="UCore-SL_Axioms_1.0_08-28-2009.xlsx"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-xlsx" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/182/=UCore-SL_Axioms_1.0_08-28-2009.xlsx" class="filelink" title="UCore-SL_Axioms_1.0_08-28-2009.xlsx"&gt;UCore-SL_Axioms_1.0_08-28-2009.xlsx&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_e8b4affefa11b90962dfce8bdaf7d21b"&gt;&lt;span class="desctext" id="fileDescDisplay_182"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;141.59 kB&lt;/td&gt;&lt;td class="col5"&gt;09:47, 17 Apr 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, 'e8b4affefa11b90962dfce8bdaf7d21b', '182', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg2"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/183/=UCore-SL_Class-Definitions_1.0_07-31-2009.xls" class="filelink" title="UCore-SL_Class-Definitions_1.0_07-31-2009.xls"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-xls" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/183/=UCore-SL_Class-Definitions_1.0_07-31-2009.xls" class="filelink" title="UCore-SL_Class-Definitions_1.0_07-31-2009.xls"&gt;UCore-SL_Class-Definitions_1.0_07-31-2009.xls&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_c5b0b80e9e5f80faefd43d2a0bfd49ed"&gt;&lt;span class="desctext" id="fileDescDisplay_183"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;45.5 kB&lt;/td&gt;&lt;td class="col5"&gt;09:47, 17 Apr 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, 'c5b0b80e9e5f80faefd43d2a0bfd49ed', '183', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg1"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/184/=UCore-SL_Relations-Definitions-OWL-DL_1.0_06-30-2009.owl" class="filelink" title="UCore-SL_Relations-Definitions-OWL-DL_1.0_06-30-2009.owl"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-unknown" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/184/=UCore-SL_Relations-Definitions-OWL-DL_1.0_06-30-2009.owl" class="filelink" title="UCore-SL_Relations-Definitions-OWL-DL_1.0_06-30-2009.owl"&gt;UCore-SL_Relations-Definitions-OWL-DL_1.0_06-30-2009.owl&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_a390bb8246e1d38bb443b71d014f3494"&gt;&lt;span class="desctext" id="fileDescDisplay_184"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;15.25 kB&lt;/td&gt;&lt;td class="col5"&gt;09:47, 17 Apr 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, 'a390bb8246e1d38bb443b71d014f3494', '184', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg2"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/185/=UCore-SL_Relations-OWL-DL_1.0_06-30-2009.owl" class="filelink" title="UCore-SL_Relations-OWL-DL_1.0_06-30-2009.owl"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-unknown" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/185/=UCore-SL_Relations-OWL-DL_1.0_06-30-2009.owl" class="filelink" title="UCore-SL_Relations-OWL-DL_1.0_06-30-2009.owl"&gt;UCore-SL_Relations-OWL-DL_1.0_06-30-2009.owl&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_36c269596a84e93ade135924cd1aa995"&gt;&lt;span class="desctext" id="fileDescDisplay_185"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;4.97 kB&lt;/td&gt;&lt;td class="col5"&gt;09:47, 17 Apr 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, '36c269596a84e93ade135924cd1aa995', '185', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg1"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/186/=UCore-SL_Taxonomy-OWL-DL_1.0_06-30-2009.owl" class="filelink" title="UCore-SL_Taxonomy-OWL-DL_1.0_06-30-2009.owl"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-unknown" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/186/=UCore-SL_Taxonomy-OWL-DL_1.0_06-30-2009.owl" class="filelink" title="UCore-SL_Taxonomy-OWL-DL_1.0_06-30-2009.owl"&gt;UCore-SL_Taxonomy-OWL-DL_1.0_06-30-2009.owl&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_a1207377ac34bb7b3931d8a8dc40a6cd"&gt;&lt;span class="desctext" id="fileDescDisplay_186"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;120.91 kB&lt;/td&gt;&lt;td class="col5"&gt;09:47, 17 Apr 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, 'a1207377ac34bb7b3931d8a8dc40a6cd', '186', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg2"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/1565/=UCORE2.0.xls" class="filelink" title="UCORE2.0.xls"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-xls" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/1565/=UCORE2.0.xls" class="filelink" title="UCORE2.0.xls"&gt;UCORE2.0.xls&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_25ce7a65c4bffd9c35ae935031891744"&gt;&lt;span class="desctext" id="fileDescDisplay_1565"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;24 kB&lt;/td&gt;&lt;td class="col5"&gt;14:18, 15 Aug 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, '25ce7a65c4bffd9c35ae935031891744', '1565', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr class="bg1"&gt;&lt;td class="col1"&gt;&amp;nbsp;&lt;/td&gt;&lt;td class="col2"&gt;&lt;a href="@api/wik/files/469/=UCoreSL_BriefingSep2009Final.pptx" class="filelink" title="UCoreSL_BriefingSep2009Final.pptx"&gt;&lt;span class="icon"&gt;&lt;img src="skins/common/icons/icon-trans.gif" class="mt-ext-pptx" alt="" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/td&gt;&lt;td class="col3"&gt;&lt;a href="@api/wik/files/469/=UCoreSL_BriefingSep2009Final.pptx" class="filelink" title="UCoreSL_BriefingSep2009Final.pptx"&gt;UCoreSL_BriefingSep2009Final.pptx&lt;/a&gt; &lt;small&gt;&lt;/small&gt;&lt;div id="class_b50659c99fd5ff3ceed389b957b7f496"&gt;&lt;span class="desctext" id="fileDescDisplay_469"&gt;&lt;span class="nodescription"&gt;No description&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="col4"&gt;503.97 kB&lt;/td&gt;&lt;td class="col5"&gt;14:53, 22 Apr 2010&lt;/td&gt;&lt;td class="col6"&gt;&lt;a href="User:Admin" class="link-user" rel="internal"&gt;Admin&lt;/a&gt;&lt;/td&gt;&lt;td class="col7"&gt;&lt;a href="#" class="downarrow actionmenu" onclick="return FileMenu.show(this, 'b50659c99fd5ff3ceed389b957b7f496', '469', false, false, false, '', true);"&gt;Actions&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;					&lt;/div&gt;
				&lt;/div&gt;
				
				&lt;div class="gallery"&gt;
					&lt;h2&gt;Images 0&lt;/h2&gt;
	 				&lt;div id="pageGalleryWrap"&gt;&lt;div class="nofiles"&gt;&amp;nbsp;&lt;/div&gt;&lt;/div&gt;				&lt;/div&gt;
				
 				&lt;div id="comments"&gt;&lt;div class="comments"&gt;&lt;div class="commentMore"&gt;Viewing 4 of 4 comments: view all&lt;/div&gt;&lt;div class="comment" id="comment10"&gt;&lt;div class="commentNum"&gt;&lt;a href="Ucore-SL#comment10"&gt;#10&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;&lt;a href="User:mortgacal" class="link-user" rel="internal"&gt;mortgacal&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm10"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText10"&gt;Hi this is good article well done,i have been searching on this thanks &lt;a href=""&gt;make money online&lt;/a&gt; &lt;a href=""&gt;mortgage calculator&lt;/a&gt; &lt;a href=""&gt;komputer&lt;/a&gt;&lt;div class="commentPosted"&gt;Posted 11:59, 25 May 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment20"&gt;&lt;div class="commentNum"&gt;&lt;a href="Ucore-SL#comment20"&gt;#20&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;Wellnesshotel SÃ¼dtirol&lt;a href="index.php?title=User:Wellnesshotel_S%C3%BCdtirol" class="new link-user" rel="internal"&gt;?&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm20"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText20"&gt;The Universal Core (UCore) is a central element of the National Information Sharing Strategy that is supported by multiple U.S. Federal Government Departments, by the intelligence community, and by a number of other national and international institutions.
&lt;a href="wellnesshotel-sudtirol.htm"&gt;Wellnesshotel SÃ¼dtirol&lt;a/&gt;
&lt;div class="commentPosted"&gt;Posted 07:18, 7 Jun 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment26"&gt;&lt;div class="commentNum"&gt;&lt;a href="Ucore-SL#comment26"&gt;#26&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;platinum protection577&lt;a href="User:platinum_protection577" class="new link-user" rel="internal"&gt;?&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm26"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText26"&gt;Nice post having excellent contents.I have been searching for this type of posts.Thanks a lot for sharing.Keep blogging.
&lt;a href=""&gt;platinum protection577&lt;a/&gt;&lt;div class="commentPosted"&gt;Posted 08:25, 25 Jun 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="comment" id="comment44"&gt;&lt;div class="commentNum"&gt;&lt;a href="Ucore-SL#comment44"&gt;#44&lt;/a&gt;&lt;/div&gt;&lt;div class="commentText"&gt;&lt;div class="commentMetaData"&gt;&lt;span&gt;application blocking&lt;a href="User:application_blocking" class="new link-user" rel="internal"&gt;?&lt;/a&gt; says:&lt;/span&gt;&lt;/div&gt;&lt;div id="commentTextForm44"&gt;&lt;/div&gt;&lt;div class="commentContent" id="commentText44"&gt;Thanks for sharing the info, keep up the good work going.... I really enjoyed exploring your site. good resource
&lt;a href="ApplicationPrioritization.html"&gt;application blocking&lt;a/&gt;
&lt;div class="commentPosted"&gt;Posted 06:43, 26 Jul 2010&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="br"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="commentMore"&gt;Viewing 4 of 4 comments: view all&lt;/div&gt;&lt;/div&gt;&lt;div class="commentForm"&gt;You must &lt;a href="index.php?title=Special:Userlogin&amp;amp;returntotitle=Ucore-SL"&gt;login&lt;/a&gt; to post a comment.&lt;/div&gt;&lt;/div&gt;								
				&lt;div class="custom custom5"&gt;
									&lt;/div&gt;
			&lt;/div&gt;
			&lt;div class="bodyFooter"&gt;
					&lt;div class="pre"&gt;&lt;/div&gt;
					&lt;div class="post"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;div class="Wik.is"&gt;&lt;div class="poweredBy"&gt;Powered by &lt;a href=""&gt; Wik.is Express: open source enterprise collaboration and wik software&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;
			&lt;div class="sourceforge" style="text-align: center; margin: 8px 0;"&gt;&lt;a href="http://wik.is/"&gt;&lt;img src="http://wik.is/wp-content/uploads/2015/06/logo1.png" alt=" Wik.is" /&gt;&lt;/a&gt;&lt;/div&gt; 		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;


&lt;script type="text/javascript"&gt;var _endtime = new Date().getTime(); var _size = 52594;&lt;/script&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuTools" style="display:none;"&gt;
	&lt;ul&gt;	&lt;li class="siteListRss"&gt;&lt;a href="Special:ListRss" title="RSS feeds"&gt;&lt;span&gt;&lt;/span&gt;RSS feeds&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteListusers"&gt;&lt;a href="User:" title="Users"&gt;&lt;span&gt;&lt;/span&gt;Users&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteListTemplates"&gt;&lt;a href="Template:" title="Templates"&gt;&lt;span&gt;&lt;/span&gt;Templates&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteSitemap"&gt;&lt;a href="Special:Sitemap" title="Sitemap"&gt;&lt;span&gt;&lt;/span&gt;Sitemap&lt;/a&gt;&lt;/li&gt;
	&lt;li class="sitePopularpages"&gt;&lt;a href="Special:Popularpages" title="Popular pages"&gt;&lt;span&gt;&lt;/span&gt;Popular pages&lt;/a&gt;&lt;/li&gt;
	&lt;li class="siteAbout"&gt;&lt;a href="Special:About" title="About"&gt;&lt;span&gt;&lt;/span&gt;About&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;	
&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuPageOptions" style="display:none;"&gt;
	&lt;ul&gt;	&lt;li class="pageEdit disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Edit page"&gt;&lt;span&gt;&lt;/span&gt;Edit page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageAdd disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');" title="New page"&gt;&lt;span&gt;&lt;/span&gt;New page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageRestrict disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Restrict access"&gt;&lt;span&gt;&lt;/span&gt;Restrict access&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageAttach disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Attach file"&gt;&lt;span&gt;&lt;/span&gt;Attach file&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageMove disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Move page"&gt;&lt;span&gt;&lt;/span&gt;Move page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageDelete disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Delete page"&gt;&lt;span&gt;&lt;/span&gt;Delete page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pagePrint "&gt;&lt;a href="index.php?title=Ucore-SL&amp;amp;action=print" onclick="menuOff('menuPageOptions');return Print.open('/index.php?title=Ucore-SL&amp;amp;action=print');" title="Print page"&gt;&lt;span&gt;&lt;/span&gt;Print page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageTags disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Tag"&gt;&lt;span&gt;&lt;/span&gt;Tag&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageEmail disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Email link"&gt;&lt;span&gt;&lt;/span&gt;Email link&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageProperties disabled"&gt;&lt;a href="#" class="disabled" onclick="menuOff('menuPageOptions');return false" title="Set page properties"&gt;&lt;span&gt;&lt;/span&gt;Set page properties&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageTalk "&gt;&lt;a href="Talk:Ucore-SL" onclick="menuOff('menuPageOptions');" title="Talk page"&gt;&lt;span&gt;&lt;/span&gt;Talk page&lt;/a&gt;&lt;/li&gt;
	&lt;li class="pageWatch "&gt;&lt;a href="index.php?title=Ucore-SL&amp;amp;action=watch" onclick="menuOff('menuPageOptions');" title="Watch page"&gt;&lt;span&gt;&lt;/span&gt;Watch page&lt;/a&gt;&lt;/li&gt;
&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuBacklink" style="display:none;"&gt;
	&lt;ul&gt;&lt;li class="first"&gt;&lt;a href=""&gt;Federal Data Web 2.0 Wiki Pilot&lt;/a&gt;&lt;/li&gt;&lt;li class="last"&gt;&lt;a href="NIEM"&gt;NIEM&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;

&lt;div onclick="DWMenu.Bubble=true;" class="menu" id="menuPageContent" style="display:none;"&gt;
	&lt;div class="pageToc"&gt;&lt;h5&gt;Table of contents&lt;/h5&gt;&lt;em&gt;No headers&lt;/em&gt;&lt;/div&gt;&lt;/div&gt;


&lt;div class="ui-msg-wrap" id="MTMessage" style="display: none;"&gt;
	&lt;div class="ui-msg ui-errormsg" id="MTMessageStyle"&gt;
		&lt;div class="ui-msg-opt"&gt;
			&lt;ul&gt;
				&lt;li&gt;&lt;a href="#" class="dismiss" onclick="return MTMessage.Hide();"&gt;dismiss message&lt;/a&gt;&lt;/li&gt;
				&lt;li&gt;&lt;a href="#" class="details" id="MTMessageDetailsLink" onclick="return MTMessage.ShowDetails(this);"&gt;view details&lt;/a&gt;&lt;/li&gt;
			&lt;/ul&gt;
			&lt;div class="ui-msg-autoclose"&gt;
				&lt;span id="MTMessageUnpaused" style="display: inline;"&gt;Message will close by itself in &lt;span id="MTMessageTimer"&gt;&lt;/span&gt; seconds&lt;/span&gt;
				&lt;span id="MTMessagePaused" style="display: none;"&gt;Message timer has been stopped&lt;/span&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		&lt;div class="ui-msg-header" id="MTMessageHeader"&gt;&lt;/div&gt;
		&lt;div class="ui-msg-desc" id="MTMessageDesc"&gt;&lt;/div&gt;
		&lt;div class="ui-msg-desc" id="MTMessageDetails" style="display: none;"&gt;
			&lt;p&gt;Viewing Details:&lt;/p&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;&lt;div id="menuFiller"&gt;&lt;/div&gt;&lt;div id="bodyHeight"&gt;&lt;/div&gt;&lt;script src="urchin.js" type="text/javascript"&gt;&lt;/script&gt;
&lt;!-- Served by ip-10-250-75-15 in 0.89 secs. --&gt;
&lt;!-- /wik/site/settings: 0.0075900554656982--&gt;
&lt;!-- /wik/users/=Anonymous: 0.37417984008789--&gt;
&lt;!-- /wik/site/services/1: 0.0046501159667969--&gt;
&lt;!-- /wik/pages/1134/contents: 0.031103134155273--&gt;
&lt;!-- /wik/pages/1134: 0.074067115783691--&gt;
&lt;!-- /wik/pages/1134/comments: 0.032256841659546--&gt;
&lt;!-- /wik/pages/1134/security: 0.016643047332764--&gt;
&lt;!-- /wik/files/1564/revisions: 0.071744918823242--&gt;
&lt;!-- /wik/files/1562/revisions: 0.097723960876465--&gt;
&lt;!-- /wik/users/=Admin: 0.0086109638214111--&gt;
&lt;!-- /wik/site/nav/=Ucore-SL/full: 0.040759086608887--&gt;
&lt;!-- Total: 0.75932908058167--&gt;
&lt;!-- Real: 0.75932908058167--&gt;

&lt;/body&gt;
  
&lt;/html&gt;</text>
    <sha1>f929c4505bd22a02cdc0f69ac43b2f834712fdcf</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Template:Glossary Term</title>
  <ns>10</ns>
  <id>176</id>
  <revision>
    <id>397</id>
    <timestamp>2016-01-14T09:24:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Glossary Term" template. It should be called in the following format: &lt;pre&gt; {{Glossary Term }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noincl..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="230" xml:space="preserve">&lt;noinclude&gt;
This is the "Glossary Term" template.
It should be called in the following format:
&lt;pre&gt;
{{Glossary Term
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>38f075260c0c407f07d3b02845a4fd514ce80021</sha1>
  </revision>
  <revision>
    <id>398</id>
    <parentid>397</parentid>
    <timestamp>2016-01-14T09:24:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="290" xml:space="preserve">&lt;noinclude&gt;&lt;/noinclude&gt;&lt;includeonly&gt;{{#set:
 |Glossary-Term={{{Glossary Term|}}}
 |Glossary-Definition={{{Glossary Definition|}}}
 |Source={{{Source}}}
 |template=SetParserValue
}} [[Category:Glossary Term]]&lt;/includeonly&gt;&lt;br /&gt;

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Info-icon.png}}</text>
    <sha1>d3405aea09207a127a419459301440202f8dcda9</sha1>
  </revision>
  <revision>
    <id>401</id>
    <parentid>398</parentid>
    <timestamp>2016-01-14T09:30:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="268" xml:space="preserve">&lt;noinclude&gt;&lt;/noinclude&gt;&lt;includeonly&gt;{{#set:
 |Glossary-Term={{{Glossary Term|}}}
 |Glossary-Definition={{{Glossary Definition|}}}
 |template=SetParserValue
}} [[Category:Glossary Term]]&lt;/includeonly&gt;&lt;br /&gt;

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Info-icon.png}}</text>
    <sha1>0498a24103deedba37898f45be6a0643b6b8b2d5</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Form:Glossary Term</title>
  <ns>106</ns>
  <id>177</id>
  <revision>
    <id>399</id>
    <timestamp>2016-01-14T09:25:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Glossary Term" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form t..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="879" xml:space="preserve">&lt;noinclude&gt;
This is the "Glossary Term" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=Glossary Term}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Glossary Term}}}
{| class="formtable"
! Glossary Term: 
| {{{field|Glossary Term}}}
|-
! Glossary Definition: 
| {{{field|Glossary Definition}}}
|-
! Source: 
| {{{field|Source}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>df218c6185f96ff080ab522bc0f0d7e76fc840c8</sha1>
  </revision>
  <revision>
    <id>402</id>
    <parentid>399</parentid>
    <timestamp>2016-01-14T09:34:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="844" xml:space="preserve">&lt;noinclude&gt;
This is the "Glossary Term" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=Glossary Term}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Glossary Term}}}
{| class="formtable"
! Glossary Term: 
| {{{field|Glossary Term}}}
|-
! Glossary Definition: 
| {{{field|Glossary Definition}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>cdb2a71209ab161e2e2bf8cc2fae4e0e42adc494</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>CRITICAL INFORMATION REQUIREMENT</title>
  <ns>0</ns>
  <id>178</id>
  <revision>
    <id>400</id>
    <timestamp>2016-01-14T09:29:33Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Glossary Term |Glossary Term=CIR }}"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="37" xml:space="preserve">{{Glossary Term
|Glossary Term=CIR
}}</text>
    <sha1>2a1a74f26ffbd00b6e045dd04e0f140cf437d7cf</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>PRIORITY INTELLIGENCE REQUIREMENT</title>
  <ns>0</ns>
  <id>179</id>
  <revision>
    <id>403</id>
    <timestamp>2016-01-14T09:34:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Glossary Term |Glossary Term=PIR }}"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="37" xml:space="preserve">{{Glossary Term
|Glossary Term=PIR
}}</text>
    <sha1>c3f0611ed83a7af7b1f1189bda11828d6fd12b02</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>File:Social Media Monitoring-1.xlsx</title>
  <ns>6</ns>
  <id>180</id>
  <revision>
    <id>404</id>
    <timestamp>2016-01-15T00:10:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Template:Property values</title>
  <ns>10</ns>
  <id>181</id>
  <revision>
    <id>405</id>
    <timestamp>2016-01-15T08:11:03Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Property values" template. It should be called in the following format: &lt;pre&gt; {{Property values }} &lt;/pre&gt; Edit the page to see the template text. &lt;/no..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="234" xml:space="preserve">&lt;noinclude&gt;
This is the "Property values" template.
It should be called in the following format:
&lt;pre&gt;
{{Property values
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>6fb30b6309458c8a43d5eb940e52be521356d08b</sha1>
  </revision>
  <revision>
    <id>406</id>
    <parentid>405</parentid>
    <timestamp>2016-01-15T08:11:15Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="366" xml:space="preserve">&lt;noinclude&gt;Use this template to list all the unique values for a given property. For more information, see: [[List the set of unique values for a property]]

== Template code ==
&lt;/noinclude&gt;&lt;includeonly&gt;{{#arraydefine: vals
 | {{#ask: [[{{{1|}}}::+]] | mainlabel =- | headers = hide |? {{{1|}}} | limit = 10000 }}
 | , | print=list, sort=asc, unique
}}&lt;/includeonly&gt;</text>
    <sha1>fe5bafc0a79b28cc0bfc284aa34e36145b693c57</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Template:Tip</title>
  <ns>10</ns>
  <id>182</id>
  <revision>
    <id>407</id>
    <timestamp>2016-01-15T08:13:15Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Tip" template. It should be called in the following format: &lt;pre&gt; {{Tip }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;includeonly&gt;{|..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="210" xml:space="preserve">&lt;noinclude&gt;
This is the "Tip" template.
It should be called in the following format:
&lt;pre&gt;
{{Tip
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>3cbee7f8f2f7e9acb42a31b7fb8e47aec01f3fda</sha1>
  </revision>
  <revision>
    <id>408</id>
    <parentid>407</parentid>
    <timestamp>2016-01-15T08:13:31Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="340" xml:space="preserve">&lt;noinclude&gt;
This is the 'Tip' template.
It should be called in the following format:
&lt;pre&gt;
{{Tip
|Extension=
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;
{{#if:{{{Extension|}}}|
'''Extension:''' {{#arraymap:{{{Extension|}}}|,|y|[[Covers extension::y]]}}
}}

'''Description:'''
[[Category:Tips]]
&lt;/includeonly&gt;</text>
    <sha1>dafd4fc65354ddd884478eb95dcfaa9d8e982062</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Template:Set</title>
  <ns>10</ns>
  <id>183</id>
  <revision>
    <id>409</id>
    <timestamp>2016-01-15T08:14:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Set" template. It should be called in the following format: &lt;pre&gt; {{Set }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;includeonly&gt;{|..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="210" xml:space="preserve">&lt;noinclude&gt;
This is the "Set" template.
It should be called in the following format:
&lt;pre&gt;
{{Set
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>48de2f01d6afa6fb79008175062085387bacca1b</sha1>
  </revision>
  <revision>
    <id>410</id>
    <parentid>409</parentid>
    <timestamp>2016-01-15T08:14:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25" xml:space="preserve">{{#set:{{{1}}}|{{{2|}}}}}</text>
    <sha1>c5edc2c0e70d1efe883c0a435dfc6ef5dce76e37</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Template:Class links</title>
  <ns>10</ns>
  <id>145</id>
  <revision>
    <id>411</id>
    <parentid>345</parentid>
    <timestamp>2016-01-15T08:18:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="226" xml:space="preserve">&lt;noinclude&gt;
This is the "Class links" template.
It should be called in the following format:
&lt;pre&gt;
{{Class links
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>0504f5a5eec900ce74d85e88b8b6e77c32741674</sha1>
  </revision>
  <revision>
    <id>412</id>
    <parentid>411</parentid>
    <timestamp>2016-01-15T08:18:32Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="88" xml:space="preserve">[[Form:{{{1}}}|Form]], [[Template:{{{1}}}|Template]] and [[:Category:{{{1}}}|Category]].</text>
    <sha1>0fd1c4321df100a64e80a7dc2a9fb20fcfd41ccb</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Reachback Operations</title>
  <ns>0</ns>
  <id>43</id>
  <revision>
    <id>413</id>
    <parentid>183</parentid>
    <timestamp>2016-01-15T17:04:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2577" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

This wiki is intended to address the need for reachback capabilities and support by practitioners. researchers, and students.  The purpose is to address several complex areas through an innovative approach between industry, academia and the military.  What we hope this lays the groundwork for  is demonstrating the vastly different environments in the military and corporate capabilities from the 'public sector's' perspective through but a deep understanding and knowledge of the military and government.  

For the purpose in this effort we refer to "Reachback Operations", and supporting full spectrum Information Operations  (degraded state).  We will accomplish this through extensive work in ensuring the ontology alignment along with developing a focused suite of tools and resources to allow adaption by others.

To be successful will require a pragmatic and real world view, and understanding of the various differences woven into the core of each. For example a Corporate capability to support military or government reachback needs, it's realized, understood, and accepted use of government attributed computers is often impossible as well undesirable and requires trusted support teams to help facilitate discrete and low intensity mission assurance.  On the other hand the military has the capability to assist an academic institution in assistance with their strategic or immediate needs in guidance.

The model is based on the National Defense University methodology for creating and managing Communities of Practice and outreach for addressing a similar area of complexity related to socio-cultural (Human Terrain) and proven extremely effective.  Subject Matter Experts (SME) will be represented by current military and government, individuals from OccamSec's Special Projects, and education.     

{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Areas of Interest =

= Hot Sheet Requests =

= Resource Library =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>c947a0f8ea1a107fc48dec4cfc146c7243b6ebb3</sha1>
  </revision>
  <revision>
    <id>414</id>
    <parentid>413</parentid>
    <timestamp>2016-01-15T17:07:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="781" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Areas of Interest =

= Hot Sheet Requests =

= Resource Library =

= Dominant Drivers =
&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>456396fa7b2fef3c2d75c22ae80372f122e81555</sha1>
  </revision>
  <revision>
    <id>415</id>
    <parentid>414</parentid>
    <timestamp>2016-01-15T17:07:56Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2599" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Areas of Interest =

= Hot Sheet Requests =

= Resource Library =

= Dominant Drivers =
This wiki is intended to address the need for reachback capabilities and support by practitioners. researchers, and students.  The purpose is to address several complex areas through an innovative approach between industry, academia and the military.  What we hope this lays the groundwork for  is demonstrating the vastly different environments in the military and corporate capabilities from the 'public sector's' perspective through but a deep understanding and knowledge of the military and government.  

For the purpose in this effort we refer to "Reachback Operations", and supporting full spectrum Information Operations  (degraded state).  We will accomplish this through extensive work in ensuring the ontology alignment along with developing a focused suite of tools and resources to allow adaption by others.

To be successful will require a pragmatic and real world view, and understanding of the various differences woven into the core of each. For example a Corporate capability to support military or government reachback needs, it's realized, understood, and accepted use of government attributed computers is often impossible as well undesirable and requires trusted support teams to help facilitate discrete and low intensity mission assurance.  On the other hand the military has the capability to assist an academic institution in assistance with their strategic or immediate needs in guidance.

The model is based on the National Defense University methodology for creating and managing Communities of Practice and outreach for addressing a similar area of complexity related to socio-cultural (Human Terrain) and proven extremely effective.  Subject Matter Experts (SME) will be represented by current military and government, individuals from OccamSec's Special Projects, and education.     


&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>a6fe4c23b2ca319a1589a97eb74f048dc6ffc952</sha1>
  </revision>
  <revision>
    <id>416</id>
    <parentid>415</parentid>
    <timestamp>2016-01-15T17:10:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2596" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Areas of Interest =

= Current Efforts =

= Resource Library =

= Dominant Drivers =
This wiki is intended to address the need for reachback capabilities and support by practitioners. researchers, and students.  The purpose is to address several complex areas through an innovative approach between industry, academia and the military.  What we hope this lays the groundwork for  is demonstrating the vastly different environments in the military and corporate capabilities from the 'public sector's' perspective through but a deep understanding and knowledge of the military and government.  

For the purpose in this effort we refer to "Reachback Operations", and supporting full spectrum Information Operations  (degraded state).  We will accomplish this through extensive work in ensuring the ontology alignment along with developing a focused suite of tools and resources to allow adaption by others.

To be successful will require a pragmatic and real world view, and understanding of the various differences woven into the core of each. For example a Corporate capability to support military or government reachback needs, it's realized, understood, and accepted use of government attributed computers is often impossible as well undesirable and requires trusted support teams to help facilitate discrete and low intensity mission assurance.  On the other hand the military has the capability to assist an academic institution in assistance with their strategic or immediate needs in guidance.

The model is based on the National Defense University methodology for creating and managing Communities of Practice and outreach for addressing a similar area of complexity related to socio-cultural (Human Terrain) and proven extremely effective.  Subject Matter Experts (SME) will be represented by current military and government, individuals from OccamSec's Special Projects, and education.     


&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>35e78b0770ac50c33a7d006721fd66ccfcd315e9</sha1>
  </revision>
  <revision>
    <id>417</id>
    <parentid>416</parentid>
    <timestamp>2016-01-15T17:21:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1199" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Areas of Interest =

= Current Efforts =

= Resource Library =

= Dominant Drivers =

* Current need by the US and NATO to identify and engage with resources for supporting overall capabilities outside normal bounds they operate either from the inability to requirement in cover and attribution protection

* Current need by the US Air Force in the area of Targeting which identified Outreach and Distributed Systems (Chapter 3)

* Current need by Academia in assisting with ensuring the the information.

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>e03a829c5f5a85c465c32035b8a4ff0599c68e7a</sha1>
  </revision>
  <revision>
    <id>421</id>
    <parentid>417</parentid>
    <timestamp>2016-01-15T17:46:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1232" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Areas of Interest =

= Current Efforts =

= Problems ==

[[Form:Problem]]

= Resource Library =

= Dominant Drivers =

* Current need by the US and NATO to identify and engage with resources for supporting overall capabilities outside normal bounds they operate either from the inability to requirement in cover and attribution protection

* Current need by the US Air Force in the area of Targeting which identified Outreach and Distributed Systems (Chapter 3)

* Current need by Academia in assisting with ensuring the the information.

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>7f62d5b091f6278d83cfda8515b7d1c7a2eeb455</sha1>
  </revision>
  <revision>
    <id>422</id>
    <parentid>421</parentid>
    <timestamp>2016-01-15T17:47:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1245" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Areas of Interest =

= Current Efforts =

= Problems =

[[Form:Problem| Pose Problem]]

= Resource Library =

= Dominant Drivers =

* Current need by the US and NATO to identify and engage with resources for supporting overall capabilities outside normal bounds they operate either from the inability to requirement in cover and attribution protection

* Current need by the US Air Force in the area of Targeting which identified Outreach and Distributed Systems (Chapter 3)

* Current need by Academia in assisting with ensuring the the information.

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>b604b5497b3786e74b26aa147d4e93aa47642fdd</sha1>
  </revision>
  <revision>
    <id>423</id>
    <parentid>422</parentid>
    <timestamp>2016-01-15T17:50:27Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* Problems */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1250" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Areas of Interest =

= Current Efforts =

= Pose Problems =

[[Form:Problem| Pose Problem]]

= Resource Library =

= Dominant Drivers =

* Current need by the US and NATO to identify and engage with resources for supporting overall capabilities outside normal bounds they operate either from the inability to requirement in cover and attribution protection

* Current need by the US Air Force in the area of Targeting which identified Outreach and Distributed Systems (Chapter 3)

* Current need by Academia in assisting with ensuring the the information.

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Target-icon.png}}
{{#set:Full_Title=Reachback Operations Supporting Cyber and the Information Environment}}</text>
    <sha1>e432722f47d4cd02ce37b300a4a3b919cbf4901f</sha1>
  </revision>
  <revision>
    <id>424</id>
    <parentid>423</parentid>
    <timestamp>2016-01-16T19:59:03Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1057" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Areas of Interest =

= Current Efforts =

= Pose Problems =

[[Form:Problem| Pose Problem]]

= Resource Library =

= Dominant Drivers =

* Current need by the US and NATO to identify and engage with resources for supporting overall capabilities outside normal bounds they operate either from the inability to requirement in cover and attribution protection

* Current need by the US Air Force in the area of Targeting which identified Outreach and Distributed Systems (Chapter 3)

* Current need by Academia in assisting with ensuring the the information.

&lt;headertabs /&gt;</text>
    <sha1>21f42588787dfbc164d0ca0ac84be379a9065811</sha1>
  </revision>
  <revision>
    <id>425</id>
    <parentid>424</parentid>
    <timestamp>2016-02-10T12:38:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1684" xml:space="preserve">__NOEDITSECTION__
[[File:Multiple Feeds.png|left|frameless|link= ]]

{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;Subject Areas
&lt;/div&gt;
|}
|}

= Areas of Interest =

= Current Efforts =

* Research: Evaluation and assessment of threat related services available. 
  Objective: Provide an online source for accessing industry offerings.
  Approach: The resources selected on unique capability or services for engagment.
  Tactic: Provide capability composable services, solutions and expertise built for purpose.
  Technique: Create a suite of selection options developed for ad hoc or support taskings.
  -Allows configuring for what is needed when needed where needed and how needed.
= Pose Problems =

[[Form:Problem| Pose Problem]]

= Resource Library =

= Dominant Drivers =

* Current need by the US and NATO to identify and engage with resources for supporting overall capabilities outside normal bounds they operate either from the inability to requirement in cover and attribution protection

* Current need by the US Air Force in the area of Targeting which identified Outreach and Distributed Systems (Chapter 3)

* Current need in corporate capabilities in operational support and access to the various government groups through consultation in assistance with ensuring the right contacts for the specific situation.

&lt;headertabs /&gt;</text>
    <sha1>a58093710750fdbb10c600d36917038604d3bd5c</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Template:Problem</title>
  <ns>10</ns>
  <id>184</id>
  <revision>
    <id>418</id>
    <timestamp>2016-01-15T17:30:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Problem" template. It should be called in the following format: &lt;pre&gt; {{Problem |Level of Concern= |Problem Statement= |Idea Proposed= |Risks= }} &lt;/pr..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="467" xml:space="preserve">&lt;noinclude&gt;
This is the "Problem" template.
It should be called in the following format:
&lt;pre&gt;
{{Problem
|Level of Concern=
|Problem Statement=
|Idea Proposed=
|Risks=
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
! Level of Concern
| {{{Level of Concern|}}}
|-
! Problem Statement
| {{{Problem Statement|}}}
|-
! Idea Proposed
| {{{Idea Proposed|}}}
|-
! Risks
| {{{Risks|}}}
|}

[[Category:Problems]]
&lt;/includeonly&gt;</text>
    <sha1>5293da48a4013e121f7f0815e7ae28f6b5068bef</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Form:Problem</title>
  <ns>106</ns>
  <id>185</id>
  <revision>
    <id>419</id>
    <timestamp>2016-01-15T17:35:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Problem" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1061" xml:space="preserve">&lt;noinclude&gt;
This is the "Problem" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=Problem}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Problem}}}
{| class="formtable"
! Level of Concern: 
| {{{field|Level of Concern|input type=dropdown|mandatory|property=Level of Concern}}}
|-
! Problem Statement: 
| {{{field|Problem Statement|mandatory|property=Problem Statement}}}
|-
! Idea Proposed: 
| {{{field|Idea Proposed|property=Idea Proposed}}}
|-
! Risks: 
| {{{field|Risks|input type=textarea|property=Risks}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>d6e0cf961df4b7626c81199a602fa0eaaf953870</sha1>
  </revision>
  <revision>
    <id>420</id>
    <parentid>419</parentid>
    <timestamp>2016-01-15T17:44:15Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1228" xml:space="preserve">&lt;noinclude&gt;
This is the 'Problem form to generate the ability for discussion or provide solutions or expert knowledge to help.  These problems should be encouraged for using in 'feel free in creating' and for generating group input and perspective. Often this leads to more than one area or issue being identified which otherwise would never have been.  

{{#forminput:form=Problem}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Problem}}}
{| class="formtable"
! Level of Concern: 
| {{{field|Level of Concern|input type=dropdown|mandatory|property=Level of Concern}}}
|-
! Problem Statement: 
| {{{field|Problem Statement|mandatory|property=Problem Statement}}}
|-
! Idea Proposed: 
| {{{field|Idea Proposed|property=Idea Proposed}}}
|-
! Risks: 
| {{{field|Risks|input type=textarea|property=Risks}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>973a71b583f88aecfc1be10ebfb24c75a3cc4c5e</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>MediaWiki:Mainpage</title>
  <ns>8</ns>
  <id>42</id>
  <revision>
    <id>426</id>
    <parentid>60</parentid>
    <timestamp>2016-02-11T18:08:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">Knowledge Center</text>
    <sha1>fc910ab57b24435649651187ab4b7fabff97d650</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Template:Manual</title>
  <ns>10</ns>
  <id>186</id>
  <revision>
    <id>427</id>
    <timestamp>2016-02-11T18:19:49Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Manual" template. It should be called in the following format: &lt;pre&gt; {{Manual }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;includeon..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="216" xml:space="preserve">&lt;noinclude&gt;
This is the "Manual" template.
It should be called in the following format:
&lt;pre&gt;
{{Manual
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>f78c87e380595d262a1fc9ac00435dee5f67a87d</sha1>
  </revision>
  <revision>
    <id>428</id>
    <parentid>427</parentid>
    <timestamp>2016-02-11T18:20:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1371" xml:space="preserve">&lt;includeonly&gt;

[[Category:Manuals]]

= Description =
{| style="width: 25em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: both; text-align:left; "
! style="text-align: center; background-color:#ccccff;" colspan="2" |&lt;big&gt;{{PAGENAME}} [ [[Special:EditData/Field Manual/{{PAGENAME}}|Edit]] ]&lt;/big&gt;
|-
!style="vertical-align:top;"|Front Cover:
| [[Image::{{{img|}}}|]] [[Image:{{{img|}}}|100px]]
|-
!FM:
| [[FM::{{{fm}}}]]
|-
!Title:
| {{ #if: {{{title}}} | [[Title::{{{title|}}}]] | }}
|-
!Series:
| {{ #if: {{{series}}} | [[Series::{{{series|}}}]] | }}
|-
!Publication Date:
| {{ #if: {{{pubdate}}} | [[publication date::{{{pubdate|}}}]] | }}
|-
!PDF download:
| {{ #if: {{{url}}} | [[URL::{{{url|}}}]] | }}
|-
!ePub download:
| {{ #if: {{{epub}}} | [[epub::{{{epub|}}}|.epub]] | }}
|-
!Kindle download:
| {{ #if: {{{kindle}}} | [[kindle::{{{kindle|}}}|.mobi]] | }}
|-
|}''
{{{description|}}}

= Cited by pages =

{{ #ask: [[Main:+]] ([[Doctrine::{{PAGENAME}}]] OR [[Source::{{PAGENAME}}]] OR [[references::{{PAGENAME}}]])
| format=table
}}

= Image Gallery =

{{ #ask: [[Image:+]] [[Source::{{PAGENAME}}]]
| format=list
}}

&lt;headertabs/&gt;

__NOEDITSECTION__
&lt;/includeonly&gt;

[[Category:Page]]
{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Document info.png}}</text>
    <sha1>327fe583727498830d46bf34de168262626f019c</sha1>
  </revision>
  <revision>
    <id>429</id>
    <parentid>428</parentid>
    <timestamp>2016-02-11T18:20:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1353" xml:space="preserve">&lt;includeonly&gt;

[[Category:Manuals]]

= Description =
{| style="width: 25em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: both; text-align:left; "
! style="text-align: center; background-color:#ccccff;" colspan="2" |&lt;big&gt;{{PAGENAME}} [ [[Special:EditData/Field Manual/{{PAGENAME}}|Edit]] ]&lt;/big&gt;
|-
!style="vertical-align:top;"|Front Cover:
| [[Image::{{{img|}}}|]] [[Image:{{{img|}}}|100px]]
|-
!FM:
| [[FM::{{{fm}}}]]
|-
!Title:
| {{ #if: {{{title}}} | [[Title::{{{title|}}}]] | }}
|-
!Series:
| {{ #if: {{{series}}} | [[Series::{{{series|}}}]] | }}
|-
!Publication Date:
| {{ #if: {{{pubdate}}} | [[publication date::{{{pubdate|}}}]] | }}
|-
!PDF download:
| {{ #if: {{{url}}} | [[URL::{{{url|}}}]] | }}
|-
!ePub download:
| {{ #if: {{{epub}}} | [[epub::{{{epub|}}}|.epub]] | }}
|-
!Kindle download:
| {{ #if: {{{kindle}}} | [[kindle::{{{kindle|}}}|.mobi]] | }}
|-
|}''
{{{description|}}}

= Cited by pages =

{{ #ask: [[Main:+]] ([[Doctrine::{{PAGENAME}}]] OR [[Source::{{PAGENAME}}]] OR [[references::{{PAGENAME}}]])
| format=table
}}

= Image Gallery =

{{ #ask: [[Image:+]] [[Source::{{PAGENAME}}]]
| format=list
}}

&lt;headertabs/&gt;

__NOEDITSECTION__
&lt;/includeonly&gt;

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Document info.png}}</text>
    <sha1>6b61e0b462c0ce8b4062a209b10ecada46b181dd</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Form:Manual</title>
  <ns>106</ns>
  <id>187</id>
  <revision>
    <id>430</id>
    <timestamp>2016-02-11T18:22:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Manual" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1014" xml:space="preserve">&lt;noinclude&gt;
This is the "Manual" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=Manual}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Manual}}}
{| class="formtable"
! Fm: 
| {{{field|fm}}}
|-
! Description: 
| {{{field|description}}}
|-
! Img: 
| {{{field|img}}}
|-
! Title: 
| {{{field|title}}}
|-
! Series: 
| {{{field|series}}}
|-
! Pubdate: 
| {{{field|pubdate}}}
|-
! Url: 
| {{{field|url}}}
|-
! Epub: 
| {{{field|epub}}}
|-
! Kindle: 
| {{{field|kindle}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>8a59cd2fc8c35628392dc68324dc5a430bbe90d2</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Knowledge Management Operations</title>
  <ns>0</ns>
  <id>188</id>
  <revision>
    <id>431</id>
    <timestamp>2016-02-11T18:23:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Manual}}"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10" xml:space="preserve">{{Manual}}</text>
    <sha1>039e99faf4648cc778d8e0f48ee0463b0f756d28</sha1>
  </revision>
  <revision>
    <id>432</id>
    <parentid>431</parentid>
    <timestamp>2016-02-11T18:24:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1522" xml:space="preserve">{{Field Manual
|img=Fm-6-01-1.png
|description=KM can be summarized in the phrase “Know, Show, Grow!” Know = tacit “head knowledge”; Show =
knowledge that is written down and documented (explicit knowledge) to be shared with others; Grow =
collaboration toward innovation which sparks new knowledge.

What individuals and small elements know that could help others cannot be widely shared without the means to
share it. The sheer volume of available information makes it difficult to identify and use that which is relevant.
Knowledge management provides the means to efficiently share knowledge, thus enabling shared understanding
and learning within organizations. To do this, KM creates, organizes, applies, and transfers knowledge and
information between authorized people. It seeks to align people, processes, and tools—to include information
technology—within the organization to continuously capture, maintain, and re-use key information and lessons
learned to help units learn and adapt and improve mission performance. KM enhances an organization’s ability
to detect and remove obstacles to knowledge flow, thereby fostering mission success. Because collaboration is
the key contributor to KM, it is imperative that everyone be involved in the process, from the generating force
that trains and sustains the Soldier to the operating force, which ensures Soldiers survive and thrive every day in
every circumstance or location.
|fm=6-01.1
|url=
|title=Knowledge Management Operations
|pubdate=2012
}}</text>
    <sha1>94021b283743343c4682ec12ba876900c23131ba</sha1>
  </revision>
  <revision>
    <id>435</id>
    <parentid>432</parentid>
    <timestamp>2016-02-11T18:27:33Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1516" xml:space="preserve">{{Manual
|img=Fm-6-01-1.png
|description=KM can be summarized in the phrase “Know, Show, Grow!” Know = tacit “head knowledge”; Show =
knowledge that is written down and documented (explicit knowledge) to be shared with others; Grow =
collaboration toward innovation which sparks new knowledge.

What individuals and small elements know that could help others cannot be widely shared without the means to
share it. The sheer volume of available information makes it difficult to identify and use that which is relevant.
Knowledge management provides the means to efficiently share knowledge, thus enabling shared understanding
and learning within organizations. To do this, KM creates, organizes, applies, and transfers knowledge and
information between authorized people. It seeks to align people, processes, and tools—to include information
technology—within the organization to continuously capture, maintain, and re-use key information and lessons
learned to help units learn and adapt and improve mission performance. KM enhances an organization’s ability
to detect and remove obstacles to knowledge flow, thereby fostering mission success. Because collaboration is
the key contributor to KM, it is imperative that everyone be involved in the process, from the generating force
that trains and sustains the Soldier to the operating force, which ensures Soldiers survive and thrive every day in
every circumstance or location.
|fm=6-01.1
|url=
|title=Knowledge Management Operations
|pubdate=2012
}}</text>
    <sha1>759eb8fd8559ad2caeedebebfca45f74088bd4fd</sha1>
  </revision>
  <revision>
    <id>439</id>
    <parentid>435</parentid>
    <timestamp>2016-02-11T18:30:15Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1555" xml:space="preserve">{{Manual
|fm=6-01.1
|description=KM can be summarized in the phrase “Know, Show, Grow!” Know = tacit “head knowledge”; Show =knowledge that is written down and documented (explicit knowledge) to be shared with others; Grow =collaboration toward innovation which sparks new knowledge.What individuals and small elements know that could help others cannot be widely shared without the means toshare it. The sheer volume of available information makes it difficult to identify and use that which is relevant.Knowledge management provides the means to efficiently share knowledge, thus enabling shared understandingand learning within organizations. To do this, KM creates, organizes, applies, and transfers knowledge andinformation between authorized people. It seeks to align people, processes, and tools—to include informationtechnology—within the organization to continuously capture, maintain, and re-use key information and lessonslearned to help units learn and adapt and improve mission performance. KM enhances an organization’s abilityto detect and remove obstacles to knowledge flow, thereby fostering mission success. Because collaboration isthe key contributor to KM, it is imperative that everyone be involved in the process, from the generating forcethat trains and sustains the Soldier to the operating force, which ensures Soldiers survive and thrive every day inevery circumstance or location.
|img=Fm-6-01-1.png
|title=Knowledge Management Operations
|pubdate=2012
|url=http://www.reachback.io/wiki/images/b/b4/Fm6-01-1.pdf
}}</text>
    <sha1>79a1c713e46552b274c2b697d464ff4db26005cf</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Template:Field Manual</title>
  <ns>10</ns>
  <id>189</id>
  <revision>
    <id>433</id>
    <timestamp>2016-02-11T18:25:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;includeonly&gt;  [[Category:Manuals]]  = Description = {| style="width: 25em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom:..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1353" xml:space="preserve">&lt;includeonly&gt;

[[Category:Manuals]]

= Description =
{| style="width: 25em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: both; text-align:left; "
! style="text-align: center; background-color:#ccccff;" colspan="2" |&lt;big&gt;{{PAGENAME}} [ [[Special:EditData/Field Manual/{{PAGENAME}}|Edit]] ]&lt;/big&gt;
|-
!style="vertical-align:top;"|Front Cover:
| [[Image::{{{img|}}}|]] [[Image:{{{img|}}}|100px]]
|-
!FM:
| [[FM::{{{fm}}}]]
|-
!Title:
| {{ #if: {{{title}}} | [[Title::{{{title|}}}]] | }}
|-
!Series:
| {{ #if: {{{series}}} | [[Series::{{{series|}}}]] | }}
|-
!Publication Date:
| {{ #if: {{{pubdate}}} | [[publication date::{{{pubdate|}}}]] | }}
|-
!PDF download:
| {{ #if: {{{url}}} | [[URL::{{{url|}}}]] | }}
|-
!ePub download:
| {{ #if: {{{epub}}} | [[epub::{{{epub|}}}|.epub]] | }}
|-
!Kindle download:
| {{ #if: {{{kindle}}} | [[kindle::{{{kindle|}}}|.mobi]] | }}
|-
|}''
{{{description|}}}

= Cited by pages =

{{ #ask: [[Main:+]] ([[Doctrine::{{PAGENAME}}]] OR [[Source::{{PAGENAME}}]] OR [[references::{{PAGENAME}}]])
| format=table
}}

= Image Gallery =

{{ #ask: [[Image:+]] [[Source::{{PAGENAME}}]]
| format=list
}}

&lt;headertabs/&gt;

__NOEDITSECTION__
&lt;/includeonly&gt;

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Document info.png}}</text>
    <sha1>6b61e0b462c0ce8b4062a209b10ecada46b181dd</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>File:Fm-6-01-1.png</title>
  <ns>6</ns>
  <id>190</id>
  <revision>
    <id>434</id>
    <timestamp>2016-02-11T18:26:03Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Property:Manual</title>
  <ns>102</ns>
  <id>191</id>
  <revision>
    <id>436</id>
    <timestamp>2016-02-11T18:28:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="112" xml:space="preserve">This is a property of type [[Has type::Page]]. It links to pages that use the form [[Has default form::Manual]].</text>
    <sha1>89541aa90d278b64dcdd6e17e94157e618d069f8</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>Category:Manuals</title>
  <ns>14</ns>
  <id>192</id>
  <revision>
    <id>437</id>
    <timestamp>2016-02-11T18:28:46Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{#default_form:Manual}}"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24" xml:space="preserve">{{#default_form:Manual}}</text>
    <sha1>4b140fb8fac77b69cae89214bd5d14940d7b7c1c</sha1>
  </revision>
</page>
<page arvcontinue="20160110200344|390">
  <title>File:Fm6-01-1.pdf</title>
  <ns>6</ns>
  <id>193</id>
  <revision>
    <id>438</id>
    <timestamp>2016-02-11T18:29:49Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Property:FM</title>
  <ns>102</ns>
  <id>194</id>
  <revision>
    <id>440</id>
    <timestamp>2016-02-11T18:30:40Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Property:Pubdate</title>
  <ns>102</ns>
  <id>195</id>
  <revision>
    <id>441</id>
    <timestamp>2016-02-11T18:30:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Date]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Date]].</text>
    <sha1>5263c8921631f25051f416df19a72490a588561e</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Property:Title</title>
  <ns>102</ns>
  <id>196</id>
  <revision>
    <id>442</id>
    <timestamp>2016-02-11T18:31:30Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Property:Publication Date</title>
  <ns>102</ns>
  <id>197</id>
  <revision>
    <id>443</id>
    <timestamp>2016-02-11T18:32:20Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Date]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Date]].</text>
    <sha1>5263c8921631f25051f416df19a72490a588561e</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Knowledge Management Operations</title>
  <ns>0</ns>
  <id>188</id>
  <revision>
    <id>444</id>
    <parentid>439</parentid>
    <timestamp>2016-02-11T18:33:42Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[FM 6-01.1]] to [[Knowledge Management Operations]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1555" xml:space="preserve">{{Manual
|fm=6-01.1
|description=KM can be summarized in the phrase “Know, Show, Grow!” Know = tacit “head knowledge”; Show =knowledge that is written down and documented (explicit knowledge) to be shared with others; Grow =collaboration toward innovation which sparks new knowledge.What individuals and small elements know that could help others cannot be widely shared without the means toshare it. The sheer volume of available information makes it difficult to identify and use that which is relevant.Knowledge management provides the means to efficiently share knowledge, thus enabling shared understandingand learning within organizations. To do this, KM creates, organizes, applies, and transfers knowledge andinformation between authorized people. It seeks to align people, processes, and tools—to include informationtechnology—within the organization to continuously capture, maintain, and re-use key information and lessonslearned to help units learn and adapt and improve mission performance. KM enhances an organization’s abilityto detect and remove obstacles to knowledge flow, thereby fostering mission success. Because collaboration isthe key contributor to KM, it is imperative that everyone be involved in the process, from the generating forcethat trains and sustains the Soldier to the operating force, which ensures Soldiers survive and thrive every day inevery circumstance or location.
|img=Fm-6-01-1.png
|title=Knowledge Management Operations
|pubdate=2012
|url=http://www.reachback.io/wiki/images/b/b4/Fm6-01-1.pdf
}}</text>
    <sha1>79a1c713e46552b274c2b697d464ff4db26005cf</sha1>
  </revision>
  <revision>
    <id>479</id>
    <parentid>444</parentid>
    <timestamp>2016-02-14T18:54:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1612" xml:space="preserve">{{Manual
|fm=6-01.1
|description=KM can be summarized in the phrase “Know, Show, Grow!” Know = tacit “head knowledge”; Show =knowledge that is written down and documented (explicit knowledge) to be shared with others; Grow =collaboration toward innovation which sparks new knowledge.What individuals and small elements know that could help others cannot be widely shared without the means toshare it. The sheer volume of available information makes it difficult to identify and use that which is relevant.Knowledge management provides the means to efficiently share knowledge, thus enabling shared understandingand learning within organizations. To do this, KM creates, organizes, applies, and transfers knowledge andinformation between authorized people. It seeks to align people, processes, and tools—to include informationtechnology—within the organization to continuously capture, maintain, and re-use key information and lessonslearned to help units learn and adapt and improve mission performance. KM enhances an organization’s abilityto detect and remove obstacles to knowledge flow, thereby fostering mission success. Because collaboration isthe key contributor to KM, it is imperative that everyone be involved in the process, from the generating forcethat trains and sustains the Soldier to the operating force, which ensures Soldiers survive and thrive every day inevery circumstance or location.
|img=Fm-6-01-1.png
|title=Knowledge Management Operations
|pubdate=2012
|url=http://www.reachback.io/wiki/images/b/b4/Fm6-01-1.pdf
}}

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=KMO.png}}</text>
    <sha1>1572c5e1bbfc3600d20077ecde2b5a52f9d2d300</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>FM 6-01.1</title>
  <ns>0</ns>
  <id>198</id>
  <revision>
    <id>445</id>
    <timestamp>2016-02-11T18:33:43Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie moved page [[FM 6-01.1]] to [[Knowledge Management Operations]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="45" xml:space="preserve">#REDIRECT [[Knowledge Management Operations]]</text>
    <sha1>298808a67755a5a246948bc05129721b35299b43</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Template:Character</title>
  <ns>10</ns>
  <id>199</id>
  <revision>
    <id>446</id>
    <timestamp>2016-02-12T05:33:39Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Character" template. It should be called in the following format: &lt;pre&gt; {{Character }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;inc..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="222" xml:space="preserve">&lt;noinclude&gt;
This is the "Character" template.
It should be called in the following format:
&lt;pre&gt;
{{Character
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>cb4b2bccec1de22895941d3fedc19b8001e6e2c1</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Knowledge Center</title>
  <ns>0</ns>
  <id>200</id>
  <revision>
    <id>447</id>
    <timestamp>2016-02-14T17:53:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "__NOEDITSECTION__ [[File:Targetfolder-red.png|left|frameless|link= ]] {| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;" | style="width:56%; c..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="577" xml:space="preserve">__NOEDITSECTION__
[[File:Targetfolder-red.png|left|frameless|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;OPERATIONS
&lt;/div&gt;
|}
|}
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>54a1693c35aac0260881331005871d8708459e03</sha1>
  </revision>
  <revision>
    <id>448</id>
    <parentid>447</parentid>
    <timestamp>2016-02-14T18:02:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="575" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|center|frameless|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;OPERATIONS
&lt;/div&gt;
|}
|}
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>02b7a5e937beb17e3074371ed215916ffd3972f5</sha1>
  </revision>
  <revision>
    <id>450</id>
    <parentid>448</parentid>
    <timestamp>2016-02-14T18:04:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="570" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;OPERATIONS
&lt;/div&gt;
|}
|}
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>30312401ab38f7036f779c9edfeb6a19d4159a09</sha1>
  </revision>
  <revision>
    <id>451</id>
    <parentid>450</parentid>
    <timestamp>2016-02-14T18:06:04Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="580" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>1d66480c6dff31264ce906260e0e330ac989f043</sha1>
  </revision>
  <revision>
    <id>452</id>
    <parentid>451</parentid>
    <timestamp>2016-02-14T18:09:47Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="670" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}
= KMO =

= Public Sector =

= Private Sector =

= Programs 

= Resources =
&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>3764b1aa90ae27a7fff329c19a11a09196b05935</sha1>
  </revision>
  <revision>
    <id>453</id>
    <parentid>452</parentid>
    <timestamp>2016-02-14T18:10:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* Private Sector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="671" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}
= KMO =

= Public Sector =

= Private Sector =

= Programs =

= Resources =
&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>7d0dc4d5656e836f9c477272bdd222112e0badfe</sha1>
  </revision>
  <revision>
    <id>454</id>
    <parentid>453</parentid>
    <timestamp>2016-02-14T18:12:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* Programs */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="674" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}
= KMO =

= Public Sector =

= Private Sector =

= Engineering =

= Resources =
&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>474a0ed2fa3a84f6617bb37b1a33b02047a933e9</sha1>
  </revision>
  <revision>
    <id>455</id>
    <parentid>454</parentid>
    <timestamp>2016-02-14T18:15:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="619" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}
= KMO =

= Resources =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>bac81ad598a38be17dcfaf1437f8f661c5d6a155</sha1>
  </revision>
  <revision>
    <id>458</id>
    <parentid>455</parentid>
    <timestamp>2016-02-14T18:19:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="626" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}
= KMO =
{{KMO}}
= Resources =

&lt;headertabs /&gt;
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>3bffb581ade957bd1a904ed42c876928a2297d8f</sha1>
  </revision>
  <revision>
    <id>459</id>
    <parentid>458</parentid>
    <timestamp>2016-02-14T18:20:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>/* Resources */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="596" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}
= KMO =
{{KMO}}
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>ecad1280eb2ba3e25484c48eb7a0ccf85fd4a098</sha1>
  </revision>
  <revision>
    <id>462</id>
    <parentid>459</parentid>
    <timestamp>2016-02-14T18:22:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="588" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}
{{KMO}}
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>cdb1984559832a130acf54ef98ee520b2a5c883d</sha1>
  </revision>
  <revision>
    <id>466</id>
    <parentid>462</parentid>
    <timestamp>2016-02-14T18:30:32Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="581" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>3c5a174c483aeb8b5168bd31a08b816cdbfcf784</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>File:World-Banner.png</title>
  <ns>6</ns>
  <id>201</id>
  <revision>
    <id>449</id>
    <timestamp>2016-02-14T18:04:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Template:KMO</title>
  <ns>10</ns>
  <id>202</id>
  <revision>
    <id>456</id>
    <timestamp>2016-02-14T18:17:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "KMO" template. It should be called in the following format: &lt;pre&gt; {{KMO }} &lt;/pre&gt; Edit the page to see the template text. &lt;/noinclude&gt;&lt;includeonly&gt;{|..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="210" xml:space="preserve">&lt;noinclude&gt;
This is the "KMO" template.
It should be called in the following format:
&lt;pre&gt;
{{KMO
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>e725d22d38ccfd2bfbdb80c3251f560dc03f83ec</sha1>
  </revision>
  <revision>
    <id>457</id>
    <parentid>456</parentid>
    <timestamp>2016-02-14T18:18:41Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1033" xml:space="preserve">&lt;includeonly&gt;

= Description =
{| style="width: 25em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: both; text-align:left; "
! style="text-align: center; background-color:#ccccff;" colspan="2" |&lt;big&gt;{{PAGENAME}} [ [[Special:EditData/Field Manual/{{PAGENAME}}|Edit]] ]&lt;/big&gt;
|-
!style="vertical-align:top;"|Front Cover:
| [[Image::{{{img|}}}|]] [[Image:{{{img|}}}|100px]]
|-
!FM:
| [[FM::{{{fm}}}]]
|-
!Title:
| {{ #if: {{{title}}} | [[Title::{{{title|}}}]] | }}
|-
!Series:
| {{ #if: {{{series}}} | [[Series::{{{series|}}}]] | }}
|-
!Publication Date:
| {{ #if: {{{pubdate}}} | [[publication date::{{{pubdate|}}}]] | }}
|-
!PDF download:
| {{ #if: {{{url}}} | [[URL::{{{url|}}}]] | }}
|-
!ePub download:
| {{ #if: {{{epub}}} | [[epub::{{{epub|}}}|.epub]] | }}
|-
!Kindle download:
| {{ #if: {{{kindle}}} | [[kindle::{{{kindle|}}}|.mobi]] | }}
|-
|}''
{{{description|}}}

&lt;headertabs/&gt;

__NOEDITSECTION__
&lt;/includeonly&gt;</text>
    <sha1>b3bb121f83eb331a87007815df215f85bdac65e2</sha1>
  </revision>
  <revision>
    <id>460</id>
    <parentid>457</parentid>
    <timestamp>2016-02-14T18:21:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1331" xml:space="preserve">&lt;includeonly&gt;

= Description =
{| style="width: 25em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: both; text-align:left; "
! style="text-align: center; background-color:#ccccff;" colspan="2" |&lt;big&gt;{{PAGENAME}} [ [[Special:EditData/Field Manual/{{PAGENAME}}|Edit]] ]&lt;/big&gt;
|-
!style="vertical-align:top;"|Front Cover:
| [[Image::{{{img|}}}|]] [[Image:{{{img|}}}|100px]]
|-
!FM:
| [[FM::{{{fm}}}]]
|-
!Title:
| {{ #if: {{{title}}} | [[Title::{{{title|}}}]] | }}
|-
!Series:
| {{ #if: {{{series}}} | [[Series::{{{series|}}}]] | }}
|-
!Publication Date:
| {{ #if: {{{pubdate}}} | [[publication date::{{{pubdate|}}}]] | }}
|-
!PDF download:
| {{ #if: {{{url}}} | [[URL::{{{url|}}}]] | }}
|-
!ePub download:
| {{ #if: {{{epub}}} | [[epub::{{{epub|}}}|.epub]] | }}
|-
!Kindle download:
| {{ #if: {{{kindle}}} | [[kindle::{{{kindle|}}}|.mobi]] | }}
|-
|}''
{{{description|}}}

= Cited by pages =

{{ #ask: [[Main:+]] ([[Doctrine::{{PAGENAME}}]] OR [[Source::{{PAGENAME}}]] OR [[references::{{PAGENAME}}]])
| format=table
}}

= Image Gallery =

{{ #ask: [[Image:+]] [[Source::{{PAGENAME}}]]
| format=list
}}

&lt;headertabs/&gt;

__NOEDITSECTION__
&lt;/includeonly&gt;

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Document info.png}}</text>
    <sha1>bb6fb7c401457c076269135837ded6d1d7eb4032</sha1>
  </revision>
  <revision>
    <id>463</id>
    <parentid>460</parentid>
    <timestamp>2016-02-14T18:26:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2188" xml:space="preserve">KM can be summarized in the phrase “Know, Show, Grow!” Know = tacit “head knowledge”; Show = knowledge that is written down and documented (explicit knowledge) to be shared with others; Grow = collaboration toward innovation which sparks new knowledge.
[{New paragraph}}
What individuals and small elements know that could help others cannot be widely shared without the means to share it. The sheer volume of available information makes it difficult to identify and use that which is relevant. Knowledge management provides the means to efficiently share knowledge, thus enabling shared understanding and learning within organizations. To do this, KM creates, organizes, applies, and transfers knowledge and information between authorized people. It seeks to align people, processes, and tools—to include information technology—within the organization to continuously capture, maintain, and re-use key information and lessons learned to help units learn and adapt and improve mission performance. KM enhances an organization’s ability to detect and remove obstacles to knowledge flow, thereby fostering mission success. Because collaboration is the key contributor to KM, it is imperative that everyone be involved in the process, from the generating force that trains and sustains the Soldier to the operating force, which ensures Soldiers survive and thrive every day in every circumstance or location.

{| style="width: 25em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: both; text-align:left; "
! style="text-align: center; background-color:#ccccff;" colspan="2" |&lt;big&gt;{{PAGENAME}} [ [[Special:EditData/Field Manual/{{PAGENAME}}|Edit]] ]&lt;/big&gt;
|-
!style="vertical-align:top;"|Front Cover:
| [[Image::{{{img|}}}|]] [[Image:{{{img|}}}|100px]]
|-
!Title:
| {{ #if: {{{title}}} | [[Title::{{{title|}}}]] | }}
|-
!Publication Date:
| {{ #if: {{{pubdate}}} | [[publication date::{{{pubdate|}}}]] | }}
|-
!PDF download:
| {{ #if: {{{url}}} | [[URL::{{{url|}}}]] | }}
|-
|}''

__NOEDITSECTION__

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Document info.png}}</text>
    <sha1>e713ef34c41c5af239385dce298146b23a389e97</sha1>
  </revision>
  <revision>
    <id>464</id>
    <parentid>463</parentid>
    <timestamp>2016-02-14T18:27:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2187" xml:space="preserve">{| style="width: 25em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: both; text-align:left; "
! style="text-align: center; background-color:#ccccff;" colspan="2" |&lt;big&gt;{{PAGENAME}} [ [[Special:EditData/Field Manual/{{PAGENAME}}|Edit]] ]&lt;/big&gt;
|-
!style="vertical-align:top;"|Front Cover:
| [[Image::{{{img|}}}|]] [[Image:{{{img|}}}|100px]]
|-
!Title:
| {{ #if: {{{title}}} | [[Title::{{{title|}}}]] | }}
|-
!Publication Date:
| {{ #if: {{{pubdate}}} | [[publication date::{{{pubdate|}}}]] | }}
|-
!PDF download:
| {{ #if: {{{url}}} | [[URL::{{{url|}}}]] | }}
|-
|}''
KM can be summarized in the phrase “Know, Show, Grow!” Know = tacit “head knowledge”; Show = knowledge that is written down and documented (explicit knowledge) to be shared with others; Grow = collaboration toward innovation which sparks new knowledge.
[{New paragraph}}
What individuals and small elements know that could help others cannot be widely shared without the means to share it. The sheer volume of available information makes it difficult to identify and use that which is relevant. Knowledge management provides the means to efficiently share knowledge, thus enabling shared understanding and learning within organizations. To do this, KM creates, organizes, applies, and transfers knowledge and information between authorized people. It seeks to align people, processes, and tools—to include information technology—within the organization to continuously capture, maintain, and re-use key information and lessons learned to help units learn and adapt and improve mission performance. KM enhances an organization’s ability to detect and remove obstacles to knowledge flow, thereby fostering mission success. Because collaboration is the key contributor to KM, it is imperative that everyone be involved in the process, from the generating force that trains and sustains the Soldier to the operating force, which ensures Soldiers survive and thrive every day in every circumstance or location.

__NOEDITSECTION__

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Document info.png}}</text>
    <sha1>7a79fc60343c8efcf10aa4f4f5914937040d6fa5</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Form:KMO</title>
  <ns>106</ns>
  <id>203</id>
  <revision>
    <id>461</id>
    <timestamp>2016-02-14T18:22:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "KMO" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit tha..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1005" xml:space="preserve">&lt;noinclude&gt;
This is the "KMO" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=KMO}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|KMO}}}
{| class="formtable"
! Fm: 
| {{{field|fm}}}
|-
! Description: 
| {{{field|description}}}
|-
! Img: 
| {{{field|img}}}
|-
! Title: 
| {{{field|title}}}
|-
! Series: 
| {{{field|series}}}
|-
! Pubdate: 
| {{{field|pubdate}}}
|-
! Url: 
| {{{field|url}}}
|-
! Epub: 
| {{{field|epub}}}
|-
! Kindle: 
| {{{field|kindle}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>622b32ff2e9ee3726ee768be0d38590d22ec15dd</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>File:Fm-6-01-1.png</title>
  <ns>6</ns>
  <id>190</id>
  <revision>
    <id>465</id>
    <parentid>434</parentid>
    <timestamp>2016-02-14T18:28:38Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie uploaded a new version of [[File:Fm-6-01-1.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Types of Knowledge</title>
  <ns>0</ns>
  <id>204</id>
  <revision>
    <id>467</id>
    <timestamp>2016-02-14T18:36:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "'''Tacit knowledge''' resides in an individual’s mind. It is the domain of individuals, not technology. All individuals have a unique, personal store of knowledge gained fro..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1478" xml:space="preserve">'''Tacit knowledge''' resides in an individual’s mind. It is the domain of individuals, not technology. All
individuals have a unique, personal store of knowledge gained from life experiences, training, and formal
and informal networks of friends and professional acquaintances. It includes learned nuances, subtleties,
and work-arounds. Intuition, mental agility, effective responses to crises, and the ability to adapt are also
forms of tacit knowledge. Leaders use tacit knowledge to solve complex problems and make decisions.
They also routinely engage subordinates’ tacit knowledge to improve organizational learning and enhance
unit innovation and performance.
{{New paragraph}}
'''Explicit knowledge''' consists of written or otherwise documented information that can be organized,
applied and transferred using digital (such as computer files) or non-digital (such as paper) means. Explicit
knowledge lends itself to rules, limits, and precise meanings. Examples of explicit knowledge include
dictionaries, official department publications (field manuals, technical manuals, tactics, techniques, and
procedures manuals, Department of the Army pamphlets) and memorandums. Explicit knowledge is
primarily used to support situational awareness and shared understanding as it applies to decisionmaking. 

Source [[Source::Knowledge Management Operations]]

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:KMO Pages]]__NOEDITSECTION__ __NOTOC__</text>
    <sha1>88856d0e48f93c06ee66a841f784c16e11089370</sha1>
  </revision>
  <revision>
    <id>468</id>
    <parentid>467</parentid>
    <timestamp>2016-02-14T18:37:12Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1478" xml:space="preserve">'''Tacit knowledge''' resides in an individual’s mind. It is the domain of individuals, not technology. All
individuals have a unique, personal store of knowledge gained from life experiences, training, and formal
and informal networks of friends and professional acquaintances. It includes learned nuances, subtleties,
and work-arounds. Intuition, mental agility, effective responses to crises, and the ability to adapt are also
forms of tacit knowledge. Leaders use tacit knowledge to solve complex problems and make decisions.
They also routinely engage subordinates’ tacit knowledge to improve organizational learning and enhance
unit innovation and performance.
{{New Paragraph}}
'''Explicit knowledge''' consists of written or otherwise documented information that can be organized,
applied and transferred using digital (such as computer files) or non-digital (such as paper) means. Explicit
knowledge lends itself to rules, limits, and precise meanings. Examples of explicit knowledge include
dictionaries, official department publications (field manuals, technical manuals, tactics, techniques, and
procedures manuals, Department of the Army pamphlets) and memorandums. Explicit knowledge is
primarily used to support situational awareness and shared understanding as it applies to decisionmaking. 

Source [[Source::Knowledge Management Operations]]

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:KMO Pages]]__NOEDITSECTION__ __NOTOC__</text>
    <sha1>fa9d1b8f234fce1bb09356388051847f2a39e2da</sha1>
  </revision>
  <revision>
    <id>475</id>
    <parentid>468</parentid>
    <timestamp>2016-02-14T18:47:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1529" xml:space="preserve">'''TACIT KNOWLEDGE''' 
&lt;br /&gt;
Tacit knowledge resides in an individual’s mind. It is the domain of individuals, not technology. All
individuals have a unique, personal store of knowledge gained from life experiences, training, and formal
and informal networks of friends and professional acquaintances. It includes learned nuances, subtleties,
and work-arounds. Intuition, mental agility, effective responses to crises, and the ability to adapt are also
forms of tacit knowledge. Leaders use tacit knowledge to solve complex problems and make decisions.
They also routinely engage subordinates’ tacit knowledge to improve organizational learning and enhance
unit innovation and performance.
{{New Paragraph}}
'''EXPLICIT KNOWLEDGE''' 
&lt;br /&gt;
Explicit knowledge consists of written or otherwise documented information that can be organized,
applied and transferred using digital (such as computer files) or non-digital (such as paper) means. Explicit
knowledge lends itself to rules, limits, and precise meanings. Examples of explicit knowledge include
dictionaries, official department publications (field manuals, technical manuals, tactics, techniques, and
procedures manuals, Department of the Army pamphlets) and memorandums. Explicit knowledge is
primarily used to support situational awareness and shared understanding as it applies to decisionmaking. 

Source [[Source::Knowledge Management Operations]]

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:KMO Pages]]__NOEDITSECTION__ __NOTOC__</text>
    <sha1>b4adae68ae597e6bdfb71cbe79338cdf8eebbcc6</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>TACIT KNOWLEDGE</title>
  <ns>0</ns>
  <id>205</id>
  <revision>
    <id>469</id>
    <timestamp>2016-02-14T18:38:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Glossary Term |Glossary Term=TACIT KNOWLEDGE |Glossary Definition=Tacit knowledge resides in an individual’s mind. It is the domain of individuals, not technology. All ind..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="735" xml:space="preserve">{{Glossary Term
|Glossary Term=TACIT KNOWLEDGE
|Glossary Definition=Tacit knowledge resides in an individual’s mind. It is the domain of individuals, not technology. All individuals have a unique, personal store of knowledge gained from life experiences, training, and formal and informal networks of friends and professional acquaintances. It includes learned nuances, subtleties, and work-arounds. Intuition, mental agility, effective responses to crises, and the ability to adapt are also forms of tacit knowledge. Leaders use tacit knowledge to solve complex problems and make decisions. They also routinely engage subordinates’ tacit knowledge to improve organizational learning and enhance unit innovation and performance.
}}</text>
    <sha1>69b96ed3259a1ece039354d87e67301ac0d0695f</sha1>
  </revision>
  <revision>
    <id>470</id>
    <parentid>469</parentid>
    <timestamp>2016-02-14T18:39:42Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="740" xml:space="preserve">{{Glossary Term
|Glossary Term=TACIT KNOWLEDGE :
|-
|Glossary Definition=Tacit knowledge resides in an individual’s mind. It is the domain of individuals, not technology. All individuals have a unique, personal store of knowledge gained from life experiences, training, and formal and informal networks of friends and professional acquaintances. It includes learned nuances, subtleties, and work-arounds. Intuition, mental agility, effective responses to crises, and the ability to adapt are also forms of tacit knowledge. Leaders use tacit knowledge to solve complex problems and make decisions. They also routinely engage subordinates’ tacit knowledge to improve organizational learning and enhance unit innovation and performance.
}}</text>
    <sha1>eab4337d28e462356b7baa3594d58407198c8c97</sha1>
  </revision>
  <revision>
    <id>471</id>
    <parentid>470</parentid>
    <timestamp>2016-02-14T18:40:20Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[Tacit knowledge]] to [[TACIT KNOWLEDGE]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="740" xml:space="preserve">{{Glossary Term
|Glossary Term=TACIT KNOWLEDGE :
|-
|Glossary Definition=Tacit knowledge resides in an individual’s mind. It is the domain of individuals, not technology. All individuals have a unique, personal store of knowledge gained from life experiences, training, and formal and informal networks of friends and professional acquaintances. It includes learned nuances, subtleties, and work-arounds. Intuition, mental agility, effective responses to crises, and the ability to adapt are also forms of tacit knowledge. Leaders use tacit knowledge to solve complex problems and make decisions. They also routinely engage subordinates’ tacit knowledge to improve organizational learning and enhance unit innovation and performance.
}}</text>
    <sha1>eab4337d28e462356b7baa3594d58407198c8c97</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>EXPLICIT KNOWLEDGE</title>
  <ns>0</ns>
  <id>206</id>
  <revision>
    <id>472</id>
    <timestamp>2016-02-14T18:41:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Glossary Term |Glossary Term=EXPLICIT KNOWLEDGE |Glossary Definition=Explicit knowledge consists of written or otherwise documented information that can be organized, applie..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="690" xml:space="preserve">{{Glossary Term
|Glossary Term=EXPLICIT KNOWLEDGE
|Glossary Definition=Explicit knowledge consists of written or otherwise documented information that can be organized, applied and transferred using digital (such as computer files) or non-digital (such as paper) means. Explicit knowledge lends itself to rules, limits, and precise meanings. Examples of explicit knowledge include dictionaries, official department publications (field manuals, technical manuals, tactics, techniques, and procedures manuals, Department of the Army pamphlets) and memorandums. Explicit knowledge is primarily used to support situational awareness and shared understanding as it applies to decision making.
}}</text>
    <sha1>2ee873b43afa81aebdfc770284f8cd838e8f3db1</sha1>
  </revision>
  <revision>
    <id>473</id>
    <parentid>472</parentid>
    <timestamp>2016-02-14T18:42:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="695" xml:space="preserve">{{Glossary Term
|Glossary Term=EXPLICIT KNOWLEDGE :
|-
|Glossary Definition=Explicit knowledge consists of written or otherwise documented information that can be organized, applied and transferred using digital (such as computer files) or non-digital (such as paper) means. Explicit knowledge lends itself to rules, limits, and precise meanings. Examples of explicit knowledge include dictionaries, official department publications (field manuals, technical manuals, tactics, techniques, and procedures manuals, Department of the Army pamphlets) and memorandums. Explicit knowledge is primarily used to support situational awareness and shared understanding as it applies to decision making.
}}</text>
    <sha1>41f8005b8e6eb4f30c3300cc4da90f0df19beeeb</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Property:Knowledge type</title>
  <ns>102</ns>
  <id>207</id>
  <revision>
    <id>474</id>
    <timestamp>2016-02-14T18:43:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">This is a property of type [[Has type::Page]].

The allowed values for this property are:
* [[Allows value::Explicit]]
* [[Allows value::Tacit]]</text>
    <sha1>d7ed289f6a1fcfe259fd71b6a2b83773e2690b0e</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>File:Document info.png</title>
  <ns>6</ns>
  <id>208</id>
  <revision>
    <id>476</id>
    <timestamp>2016-02-14T18:51:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Template:Glossary Term</title>
  <ns>10</ns>
  <id>176</id>
  <revision>
    <id>477</id>
    <parentid>401</parentid>
    <timestamp>2016-02-14T18:52:48Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="271" xml:space="preserve">&lt;noinclude&gt;&lt;/noinclude&gt;&lt;includeonly&gt;{{#set:
 |Glossary-Term={{{Glossary Term|}}}
|-
 |Glossary-Definition={{{Glossary Definition|}}}
 |template=SetParserValue
}} [[Category:Glossary Term]]&lt;/includeonly&gt;&lt;br /&gt;

{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon=Info-icon.png}}</text>
    <sha1>c877d0fd0588af8a0487324ea80b326d069672af</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>File:KMO.png</title>
  <ns>6</ns>
  <id>209</id>
  <revision>
    <id>478</id>
    <timestamp>2016-02-14T18:53:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>MediaWiki:Gadgets-definition</title>
  <ns>8</ns>
  <id>210</id>
  <revision>
    <id>480</id>
    <timestamp>2016-02-14T18:59:33Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "== interface-gadgets == * site[ResourceLoader|default|top|dependencies=mediawiki.legacy.wikibits,mediawiki.util,jquery.mwExtension,ext.gadget.enwp-boxes]|site.js|site.css|NavF..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1906" xml:space="preserve">== interface-gadgets ==
* site[ResourceLoader|default|top|dependencies=mediawiki.legacy.wikibits,mediawiki.util,jquery.mwExtension,ext.gadget.enwp-boxes]|site.js|site.css|NavFrame.js|NavFrame.css
* enwp-boxes[ResourceLoader|default|top]|enwp-boxes.css
* collapsibleTables[ResourceLoader|default]|collapsibleTables.js
* Edittop[ResourceLoader]|edittop.js
* UTCLiveClock[ResourceLoader]|UTCLiveClock.js
* rtrc[ResourceLoader]|rtrc.css|rtrc.js
* ajaxrecentchanges[ResourceLoader|dependencies=jquery.spinner]|ajaxrecentchanges.js
* Navigation_popups[ResourceLoader]|popups.js|navpop.css
* CodeReview_checkedRevsExport[ResourceLoader]|CodeReview_checkedRevsExport.js
* contribsrange[ResourceLoader]|contribsrange.js
* Numerakri[ResourceLoader|dependencies=jquery.cookie, mediawiki.util, mediawiki.user, mediawiki.RegExp]|Numerakri.css|Numerakri.js
* externalsearch[ResourceLoader]|externalsearch.js
* externalsearch-bar[ResourceLoader]|externalsearch-bar.js
* vector-headanchor[ResourceLoader]|vector-headanchor.js|vector-headanchor.css
* BugStatusUpdate[ResourceLoader]|BugStatusUpdate.js
* purgetab[ResourceLoader|dependencies=mediawiki.util]|purgetab.js
* Coloredlinks|Coloredlinks.css
* autolink[ResourceLoader]|autolink.js
* predefined-summaries[ResourceLoader|dependencies=mediawiki.util]|predefined-summaries.js

== editing-gadgets ==
* DotsSyntaxHighlighter[ResourceLoader|dependencies=jquery.client]|DotsSyntaxHighlighter.js
* Edittools[ResourceLoader|default]|Edittools.js
* HotCat[ResourceLoader]|HotCat.js
* TabOverride[ResourceLoader]|TabOverride.js
* oldeditor[ResourceLoader]|oldeditor.js
* workinprogress[ResourceLoader]|workinprogress.js
* userMessages[ResourceLoader]|userMessages.js

== AuthorizedUsers ==
* CleanDeleteReasons[ResourceLoader]|CleanDeleteReasons.js
* blocktab[ResourceLoader|dependencies=mediawiki.util,mediawiki.Title]|blocktab.js
* botRollback[ResourceLoader]|botRollback.js</text>
    <sha1>b2a7d5bf3bd396f8b16725eaa525198548ff6f69</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Category:KMO Pages</title>
  <ns>14</ns>
  <id>211</id>
  <revision>
    <id>481</id>
    <timestamp>2016-02-14T19:07:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "__HIDDENCAT__"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">__HIDDENCAT__</text>
    <sha1>183b9c38bff80327776bd180634fccfd19cf616f</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Gestalt Wiki Framework</title>
  <ns>0</ns>
  <id>212</id>
  <revision>
    <id>483</id>
    <parentid>482</parentid>
    <timestamp>2016-02-14T19:09:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3872" xml:space="preserve">{{Breadcrumb}}
&lt;div class="row" &gt;&lt;div class="large-8 columns"&gt;The '''[[Contact|Gestalt Wiki Framework]]''' (GWF) is a set of patterns and open source software that enables groups to build enterprise knowledge using structured wikis. This is our showcase for both ''enterprise knowledge stewards'' who are interested in wiki-based knowledge management and ''wiki builders'' who want to learn how to use GWF extensions. 
{{New Paragraph}}
Enterprise knowledge stewards may want to read more about the [[Background |background]] of the evolution and use of GWF in the enterprise as well as [[Enterprise Collaboration |enterprise collaboration with wikis]] and how enterprise content becomes a [[Content Networks|content network]].  Wiki-based enterprise knowledge management using GWF involves authors contributing content using forms.  These contributions may be combined with enterprise data,  queried, and visualized. Visualizations include automatically computed tables, tag clouds, bar charts, pie charts, time lines, calendars, and network graphs to enable readers to see the "big picture" of enterprise community knowledge. GWF allows authors to contribute content once and use that content in many ways.  The name "Gestalt" was chosen to reflect the evolving "big picture" of enterprise knowledge as communities collaboratively create, combine, and use their collective contributions towards a greater purpose.
{{New Paragraph}}
Wiki builders may be interested in jumping ahead to the [[Gestalt Wiki Framework Extensions|extensions documentation section]]. As a showcase for GWF extensions, we used many extension features throughout the site. For example, the green asterisk logo next to the title of this page is an example of the [[Title Icon]] extension.The information contained in the Table of Contents on the right is used in the green breadcrumb bar at the top of this page to help users navigate pages sequentially. Both the Table of Contents and the breadcrumbs are features provided by the [[Hierarchy Builder]] extension.
{{New Paragraph}}
Our team has built over 70 unique wikis since 2006. Half of these wikis are currently actively used at MITRE and on customer networks. Enterprise wiki collaboration is different than Wikipedian collaboration. Many enterprises lack 100,000+ volunteer editors with an evolved wiki culture. We have found that in addition to adapting wiki technology to the enterprise,  wiki success occurs when a community champion successfully articulates the purpose of a wiki and transforms existing business processes away from the dependency on document-based email collaboration. Read more about [[Enterprise Collaboration|enterprise collaboration]] and how wikis can help.
&lt;!--
As shown in the interactive [[Table of Contents]] on the right, this site is organized into three sections. The first section describes the [[Background |background]] of the GWF, as well as two concepts: how [[Enterprise Collaboration |enterprise collaboration]] can be conducted using a wiki and how the structure of the content becomes a [[Content Networks |network]]. The second section documents selected [[Gestalt Wiki Framework Extensions |extensions]] and provides working examples. The third section includes additional information about our [[Publications|publications]], [[Team|team]], [[MITRE|enterprise]], and [[Contact |contact information]].--&gt;
&lt;/div&gt;&lt;div class="large-4 columns" style="font-size:70%;background: white !important;"&gt;[[Image:GWFAuthoringMosaic.png|400px]]&lt;br&gt;Gestalt: The whole is greater than the sum of its parts.&lt;br&gt;{{#hierarchySubtree:Table of Contents|Table of Contents|Hierarchy Data|displaynameproperty=Name|showroot}}
&lt;/div&gt;&lt;/div&gt; 
----
There are [[Special:Statistics|{{NUMBEROFPAGES}}]] pages in this wiki. 
[[To do]]
{{DISPLAYTITLE:Gestalt Wiki Framework}}
{{#set:Name={{PAGENAME}}}}__NOTOC__
[[Category:Page]]</text>
    <sha1>09e70b09e205cbb4e8b74ca9972dbc3f8e81c297</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Background</title>
  <ns>0</ns>
  <id>213</id>
  <revision>
    <id>485</id>
    <parentid>484</parentid>
    <timestamp>2016-02-14T19:09:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3948" xml:space="preserve">{{Breadcrumb}}
&lt;div class="row" &gt;&lt;div class="large-12 columns"&gt;The broad enterprise encyclopedia, MITREpedia, was established in 2004 as a grassroots effort to capture technical enterprise knowledge as linked articles rather than bulleted presentations. The linear nature of slide presentations, however, forces authors to reduce complex subjects to a set of bullet items that are too weak to support decision-making or show the complexity of an issue. Information designer and visualization expert Edward Tufte has argued that bulleted presentations encourages simplistic thinking where ideas are squashed into lists and stories are transformed into a collection of disparate points&lt;ref&gt;See Wikipedia' article about [http://en.wikipedia.org/wiki/Edward_Tufte#Criticism_of_PowerPoint Edward Tufte views on bullet-based presentations]&lt;/ref&gt;. 
{{New Paragraph}}
MITREpedia project governance was led by a MITREpedia Users Group consisting of staff content providers and MITREpedia system administrators. As a grassroots volunteer encyclopedia, MITREpedia's structure evolved over time with the development of categories as a by-product of authoring articles. Navigational elements to improve findability included a featured article, recent contributions, categories, and enterprise "fast jumps"-- named enterprise links. Topic-specific "wiki portals," a major findability element for Wikipedia, were not adopted.
{{New Paragraph}}
The Gestalt Wiki Framework (GWF) effort began as a single Semantic MediaWiki-based wiki about human language technology (HLT) in 2006. The purpose was to produce a dynamic, growing knowledge repository for MITRE's work in HLT to maintain continuous enterprise situational awareness, i.e. "the big picture or "Gestalt" about HLT at MITRE without creating periodic surveys, scheduling meetings, conducting enterprise searches, and analyzing financial project data. Languapedia's sidebar was customized for the HLT community to link to projects, people, events, and HLT topics. &lt;/div&gt;&lt;/div&gt;
&lt;div class="row" &gt;&lt;div class="large-4 columns"&gt;Librarian staff discovered Languapedia after searching for an approach to develop a highly structured, highly findable biosecurity collection.  Biopedia was the second wiki to be constructed. Robopedia, the third wiki, grew at a significantly more rapid pace than Languapedia nor Biopedia. Languapedia was established as an experiment without socialization within the community. Biopedia was developed as part of a diffuse group's needs to establish biosecurity as an important up and coming interest. Robopedia represented the needs of a dedicated group of technologists who depend heavily on technical documentation. It currently contains ~8,800 pages, has ~150 users, and won a MITRE Knowledge Management Award in 2012. Robopedia became the poster wiki for many GWF wikis developed at MITRE as well as GWF wikis developed for MITRE customers. &lt;/div&gt;&lt;div class="large-8 columns"&gt;[[Image:Reuse.png|800px]]&lt;br&gt;Gestalt Wiki Influence Path&lt;/div&gt;&lt;/div&gt;
&lt;div class="row" &gt;&lt;div class="large-12 columns"&gt;As the team grew from one to seven, we developed best practices for GWF extension development as well as wiki and wiki farm development to help us work across multiple funding sources and customers simultaneously. In 2014, MITREpedia was transitioned to the McLean, VA Gestalt Wiki Framework team. It was upgraded from MediaWiki 1.13 to 1.23 from XML page exports because the MySQL database was so old that the update script failed to run. With MITREpedia's 25,000 pages, we have 60,000 pages on active wikis and 57,000 pages in read-only archive. Our vision is to work towards federating all the Gestalt Wiki Framework wikis with MITREpedia as the entry point for enterprise wiki knowledge and the topic-specific wikis.  Learn more about today's [[Gestalt Wiki Framework]]. &lt;/div&gt;&lt;/div&gt;
----
{{RefList}}
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>0c789e2fdfef1ab499622b1036a62a690a53f052</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Enterprise Collaboration</title>
  <ns>0</ns>
  <id>214</id>
  <revision>
    <id>487</id>
    <parentid>486</parentid>
    <timestamp>2016-02-14T19:09:52Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2942" xml:space="preserve">{{Breadcrumb}}
&lt;div class="row" &gt;&lt;div class="large-8 columns"&gt;Traditionally, enterprise knowledge work business processes involve staff creating a document, spreadsheet, or briefing and then emailing it to a group for review. Each time the information container is emailed to an author, an additional copy of the resource is created. Multiple copies of the information container at different stages of the editing process is copied to each author's desktop, email queue, and/or shared folders. To bring all of the modifications into a single instance of the information container, authors need to accept and merge changes. When the group of authors is highly active, it can be very time-consuming to ensure that all changes are correctly considered, accepted, and merged. Searching through large email folders to find the most current version can also be time-consuming. A document management system can improve multi-author editing using a check in and check out process. However, over time, the hierarchical structure of the document management system can become saturated with so many items that authors find it difficult to navigate or find the information containers they need.&lt;/div&gt;
&lt;div class="large-4 columns"&gt;[[Image:NxNAuthoring.png|400px]]&lt;br&gt;Emailing Knowledge Resources&lt;/div&gt;&lt;/div&gt; 
&lt;div class="row" &gt;&lt;div class="large-8 columns"&gt;Collaborating on a common page or set of pages in a wiki can eliminate the version control and findability problems cited above. Instead of emailing or posting the resource to a document management system, authors use a wiki to shape the resource. All edits are logged and authors can inspect the history of the page to learn how the page has changed over time and who were the authors who made the changes. There is no need to merge edits. Merge happens each time an author edits the page. Not only can these authors inspect the page history, they can also make comments or discuss the page. A structured wiki adds support to the authoring process by ensuring that authors edit the latest version and by authors embedding queries to aggregate and filter related knowledge, and display query results as tag clouds, bar charts, network graphs, faceted navigation lists, scatter plots, tree maps, geospatial maps, timelines, calendars, and more. Enterprise wiki champions have redirected their community members from email to make contributions about work in progress or the results of meetings with customers in the community wiki. Over time, these contributions can be aggregated on community member pages, projects pages, or any other related pages where a visualization would be useful. This is possible because structured wikis enable [[Content Networks|content networks]] to be formed and used. &lt;/div&gt;&lt;div class="large-4 columns"&gt;[[Image:GWFAuthoring.png|400px]]&lt;br&gt;Enterprise Wiki Collaboration&lt;/div&gt;&lt;/div&gt; 
----
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>6f02dac07c3304ae6aef7c4d94f0ae991a11539b</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Content Networks</title>
  <ns>0</ns>
  <id>215</id>
  <revision>
    <id>489</id>
    <parentid>488</parentid>
    <timestamp>2016-02-14T19:09:52Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3161" xml:space="preserve">{{Breadcrumb}}
&lt;div class="row" &gt;&lt;div class="large-5 columns"&gt;Enterprise content is a network of relationships between projects, events, organizations, customers, reviews, events and topics of interest to its staff, partners, and customers. There are many information technologies that can be used to reveal these relationships. This diagram captures the increasing data controls and opportunities to collaborate with more contributors. A {{Elink|http://en.wikipedia.org/wiki/Table_(information)|table}} organizes data into rows and columns. Rows represent an item and columns represent attributes or properties of the item. The intersection of a row and a column is a cell. Cells contain data values. Data controls are limited to sorting actions. A {{Elink|http://en.wikipedia.org/wiki/Spreadsheet|spreadsheet}} is a software application used to analyze data. It consists of a set of tables with enhanced controls such as functions which can modify data values using rules pivot tables which summarize and visualize data. &lt;/div&gt;&lt;div class="large-7 columns"&gt;[[Image:TableCellsToRelationships.png|700px]] &lt;br&gt; Table Cells to Structured Wikis&lt;/div&gt;&lt;/div&gt;
&lt;div class="row" &gt;&lt;div class="large-12 columns"&gt;{{Elink|http://en.wikipedia.org/wiki/Database|Databases}} use metadata in a schema to structure and organize information as queriable tables. {{Elink|http://en.wikipedia.org/wiki/Document_management_system|Document management systems}} organize documents into hierarchies where text can be searched. A wiki represents information as a collection of linked pages. Pages can be grouped by categories and edit history is logged. A structured wiki enables authors to annotate page text with user-defined properties. These properties define relationships which can be combined and queried to produce many different views of the same information.&lt;/div&gt;&lt;/div&gt;
&lt;div class="row" &gt;&lt;div class="large-5 columns"&gt;Wikis transform a single page into a network of content. For example, a wiki could contain pages about presentations created at MITRE. A form could be used to enter the information about a presentation such as the soon-to-be famous movie, "Wikis Save MITRE." The movie could be reviewed where the reviewer could rate the movie using stars and include a comment. The movie could also be discussed or commented upon where viewers engage in a dialogue about the movie. The quality of the content about the movie could also be reviewed. Finally, readers could make lists of movies and include this movie.  One wiki page about the movie item can become a network of related pages that quality or further describe the movie. In addition, the annotations in the "Wikis Save MITRE" page such as the date, time, length, description, and tags could queried and the results embedded into additional pages about the movie. To make use of iconography to improve comprehension, to visualize content as a network or hierarchy, or to rate content, see [[Gestalt Wiki Framework Extensions]].&lt;/div&gt;&lt;div class="large-7 columns"&gt;[[Image:NetworkofPages.png|700px]]&lt;br&gt;Content Network&lt;/div&gt;&lt;div&gt;
----
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>da50b9cad5ce09385ac2942d120ac9c749bdac6b</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Gestalt Wiki Framework Extensions</title>
  <ns>0</ns>
  <id>216</id>
  <revision>
    <id>491</id>
    <parentid>490</parentid>
    <timestamp>2016-02-14T19:09:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1104" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
&lt;div class="row" &gt;&lt;div class="large-6 columns"&gt;
==== Description ====
The Gestalt Wiki Framework team has written over 40 extensions for MediaWiki and Semantic MediaWiki.  Eleven extensions have been contributed to the MediaWiki open source community as shown at the bottom of this page which was transcluded page from [http://www.mediawiki.org/wiki/Category:Extensions_by_MITRE MediaWiki.org]. As our extensions mature, we plan to contribute as many general purpose extensions to the MediaWiki community as funding priorities allow.  This section of the wiki provides usage documentation as well as live examples of selected GWF extensions.  As shown in the legend, the grey boxes display the wiki text, the blue boxes contain live examples, and the white boxes are links to live examples. Visit our documentation pages: {{#hierarchyChildren:Gestalt Wiki Framework Extensions|Table of Contents|Hierarchy Data|Name|template=X}}&lt;/div&gt;&lt;div class="large-6 columns"&gt;{{Legend}}&lt;/div&gt;&lt;/div&gt;
----
[[Category:Page]]
{{#set:Name={{PAGENAME}}}} 
{{#set:Title Icon={{PAGENAME}}.png}}</text>
    <sha1>04ea82d1f66b2c852f9482fe8f4b9b06913a8c05</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Title Icons in Page</title>
  <ns>0</ns>
  <id>217</id>
  <revision>
    <id>493</id>
    <parentid>492</parentid>
    <timestamp>2016-02-14T19:09:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="171" xml:space="preserve">{{Breadcrumb}}
{{#set:Title Icon=UnderConstruction.png}}
{{#set:Title Icon=Article.png}}
{{#set:Title Icon=Inproceedings.png}}
{{#set:Name={{PAGENAME}}}}
[[Category:Page]]</text>
    <sha1>3832b0804d1c7db067791b0abda46d84058398d5</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Title Icons in Page and Category</title>
  <ns>0</ns>
  <id>218</id>
  <revision>
    <id>495</id>
    <parentid>494</parentid>
    <timestamp>2016-02-14T19:09:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="204" xml:space="preserve">{{Breadcrumb}}
{{#set:Title Icon=UnderConstruction.png}}
{{#set:Title Icon=Article.png}}
{{#set:Title Icon=Inproceedings.png}}
[[Category:Title Icon Category]]
{{#set:Name={{PAGENAME}}}}
[[Category:Page]]</text>
    <sha1>2422850acbebabbd542fe5da52d07b9411c48d6d</sha1>
  </revision>
</page>
<page arvcontinue="20160211183040|440">
  <title>Hide All Title Icons</title>
  <ns>0</ns>
  <id>219</id>
  <revision>
    <id>497</id>
    <parentid>496</parentid>
    <timestamp>2016-02-14T19:09:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="233" xml:space="preserve">{{Breadcrumb}}
{{#set:Hide Title Icon=all}}
{{#set:Title Icon=UnderConstruction.png}}
{{#set:Title Icon=Article.png}}
{{#set:Title Icon=Inproceedings.png}}
[[Category:Title Icon Category]]
{{#set:Name={{PAGENAME}}}}
[[Category:Page]]</text>
    <sha1>5d215b43cf5834c8198393b685fe8b7686067ccd</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Hide Page Title Icons</title>
  <ns>0</ns>
  <id>220</id>
  <revision>
    <id>499</id>
    <parentid>498</parentid>
    <timestamp>2016-02-14T19:09:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="235" xml:space="preserve">{{Breadcrumb}}
{{#set:Hide Title Icon=page}}
{{#set:Title Icon=UnderConstruction.png}}
{{#set:Title Icon=Article.png}}
{{#set:Title Icon=Inproceedings.png}}
 [[Category:Title Icon Category]]
{{#set:Name={{PAGENAME}}}}
[[Category:Page]]</text>
    <sha1>0f8e3d0de4d9ec150e1db4be3d26bef072fb02c1</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Hide Category Title Icon</title>
  <ns>0</ns>
  <id>221</id>
  <revision>
    <id>501</id>
    <parentid>500</parentid>
    <timestamp>2016-02-14T19:09:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="239" xml:space="preserve">{{Breadcrumb}}
{{#set:Hide Title Icon=category}}
{{#set:Title Icon=UnderConstruction.png}}
{{#set:Title Icon=Article.png}}
{{#set:Title Icon=Inproceedings.png}}
 [[Category:Title Icon Category]]
{{#set:Name={{PAGENAME}}}}
[[Category:Page]]</text>
    <sha1>617f488b4cc42ab8c47c3eb09c5e4e72a0468f80</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Semantic Rating</title>
  <ns>0</ns>
  <id>222</id>
  <revision>
    <id>503</id>
    <parentid>502</parentid>
    <timestamp>2016-02-14T19:09:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5530" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
====Description====
&lt;div class="row"&gt;&lt;div class="large-6 columns"&gt;The Semantic Rating extension adds a [http://www.mediawiki.org/wiki/Extension:Semantic_Forms Semantic Form] input type to enable users to enter a rating by clicking on stars. It also adds three parser functions to display a star rating by displaying empty (gray), full (yellow), and half stars:

* &lt;code&gt;#rating&lt;/code&gt; displays a rating inline
* &lt;code&gt;#ratingBeforeTitle&lt;/code&gt; displays a rating to the left of the title at the top of the page. 
* &lt;code&gt;#ratingAfterTitle&lt;/code&gt; displays a rating to the right of the title at the top of the page. 
__TOC__&lt;/div&gt;&lt;div class="large-6 columns"&gt;{{Legend}}&lt;/div&gt;&lt;/div&gt;
====Usage: Define a Semantic Form Rating Field====
The following will add an input field with the default maximum number of stars:
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
&lt;pre&gt;
{{{field|Rating|input type=rating}}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;"
| See working example  [[Special:FormEdit/Review/Review:1/Bclemente |An example Review Form]], See form here: [[Form:Review]]
|}
&lt;/div&gt;&lt;/div&gt;
The maximum number of stars can be set explicitly with the '''max''' parameter:
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
&lt;pre&gt;
{{{field|Rating|input type=rating|max=10}}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;"
|See working example in action ????See form here: ????
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Display a Number as a Five Star Rating====
The following displays a number as a five star rating.
&lt;div class="row" width=100% &gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:75%;"&gt;
&lt;pre&gt;
{{#rating:0}}&lt;br&gt;
{{#rating:0.5}}&lt;br&gt;
{{#rating:1}}&lt;br&gt;
{{#rating:1.5}}&lt;br&gt;
{{#rating:2}}&lt;br&gt;
{{#rating:2.5}}&lt;br&gt;
{{#rating:3}}&lt;br&gt;
{{#rating:3.5}}&lt;br&gt;
{{#rating:4}}&lt;br&gt;
{{#rating:4.5}}&lt;br&gt;
{{#rating:5}}&lt;br&gt;
{{#rating:}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;

{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#rating:0}}&lt;br&gt;
{{#rating:0.5}}&lt;br&gt;
{{#rating:1}}&lt;br&gt;
{{#rating:1.5}}&lt;br&gt;
{{#rating:2}}&lt;br&gt;
{{#rating:2.5}}&lt;br&gt;
{{#rating:3}}&lt;br&gt;
{{#rating:3.5}}&lt;br&gt;
{{#rating:4}}&lt;br&gt;
{{#rating:4.5}}&lt;br&gt;
{{#rating:5}}&lt;br&gt;
{{#rating:}}
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Display a Rating with Maximum Number of Stars====
To explicitly set the maximum number of stars to 10, use the following:
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#rating:3|10}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;

{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#rating:3|10}}
|}
&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Display an Average Rating====
The following query displays the rating using the Semantic Result Format ''average''.
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;

{{#rating:{{#ask:[[Category:Reviews]][[Item::Item:1]]|?Rating|format=average}}}} 

&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;

{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#rating:{{#ask:[[Category:Reviews]][[Item::Item:1]]|?Rating|format=average}}}}
|}
&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Display Review Results as an Average Rating====
This query displays the average rating for each item.
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
&lt;pre&gt;
{{#ask:[[Category:Items]]
|?Responsive Citation
|headers=hide
|mainlabel=-
|format=table
|class=border
|limit=5
|sort=Sorting Title
|order=ascending
| searchlabel=
}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:90%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;font-size:90%"
|{{#ask:[[Category:Items]]
|?Responsive Citation
|headers=hide
|mainlabel=-
|format=table
|class=border
|limit=5
|sort=Sorting Title
|order=ascending
| searchlabel=
}}
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Rating Before Title====
To explicitly set the number of stars to be displayed ''before'' the page title, use
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
&lt;pre&gt;
{{#ratingBeforeTitle:5}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;

{| style="border: solid 1px #D0D0D0;"
| See working example on this page: [[Rating Before Title]]
|}
&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Rating After Title====
To explicitly set the number of stars to be displayed ''after'' the page title, use
&lt;div class="row" width=100%&gt;&lt;div class="large-4 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
&lt;pre&gt;
{{#ratingAfterTitle:3}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-7 columns" style="font-size:80%;"&gt;

{| style="border: solid 1px #D0D0D0;"
| See working example on this page: [[Rating After Title]]
|}
&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:Semantic Rating}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>8d130498264bbc007c7cb981c773f442722b1d22</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>VIKI Network Graph</title>
  <ns>0</ns>
  <id>223</id>
  <revision>
    <id>505</id>
    <parentid>504</parentid>
    <timestamp>2016-02-14T19:09:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4772" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
====Description====
&lt;div class="row" style="background:white;" width=100%&gt;&lt;div class="large-5 columns" &gt;
'''VIKI''' (Visualization and Knowledge Integration) is an extension that displays the structure of wiki content as the inbound, outbound, and second order links for a list of wiki pages. It was implemented using D3 as a directed force layout graph visualization. In a VIKI graph, graph nodes represent individual wiki pages or web pages, while links between nodes indicate page links (i.e. one page has a hyperlink to another page, e.g. of the form &lt;nowiki&gt;[[Page Link]]&lt;/nowiki&gt;). These links are directional, where the direction of the link indicates which page links to which. If two pages link to each other, the link is bidirectional. Two pages are linked on a VIKI graph if there is a link between their nodes on the graph, i.e. either of the two pages links to the other, or they link to each other. Some wiki pages also have hyperlinks to external web pages; these pages are also displayed on the VIKI graph (with a generic wi-fi icon), but interaction with these pages is limited.
{{New Paragraph}}
The graph is pannable and zoomable using either the mouse scroll action or the zoom bar located at the bottom of the graph. Individual nodes may be dragged around and rearranged as well; the D3 graph automatically revises node positions to a local equilibrium state whenever nodes are dragged.
&lt;/div&gt;&lt;div class="large-7 columns" style="border: solid 1px #E8E8E8;background:#ADDFFF;"&gt;
{{New Paragraph}}
{{#viki:pageTitles=Gestalt Wiki Framework Extensions|width=490|height=490}}
&lt;/div&gt;&lt;/div&gt;
The graph is first initialized with a (user-defined) list of wiki pages, along with all pages linked to these pages. Pages linked to this secondary level of pages are not initially displayed – only the first order links are initially present. The user may then choose to elaborate a node; elaboration involves retrieving and displaying all linked pages for the given node’s page. Elaboration of a node expands the VIKI graph, and users may expand the graph to explore the structure of the wiki. Elaborated nodes are also called hub nodes, and the length of links to hub nodes is longer for improved graph visibility. Users may also choose to hide individual nodes and/or hide entire hubs to focus down the graph to areas of interest.
====Usage====
Users may right click on a given node to bring up a context menu of options. Below is a list of all possible options, but not all nodes may have all options as appropriate.
* ''Freeze'': this node becomes frozen in position while other nodes may move around it
* ''Visit Page'': opens the page represented by the node in a new tab or window
* ''Elaborate'': elaborates a node, as discussed previously
* ''Show Categories'': Pops up a JavaScript alert listing the categories this page belongs to. (Under construction.)
* ''Hide Node'': Removes this node and links to it from the VIKI graph.
* ''Hide Hub'': Removes this hub node and all nodes immediately linked to it from the VIKI graph, unless the linked node is itself a hub.
* ''Show All'': Adds all previously-hidden nodes and links back into the VIKI graph.

To embed a VIKI graph into a page,  the following parser function syntax is used:

&lt;div class="row" width=100%&gt;&lt;div class="large-12 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:90%;"&gt;
 &lt;pre&gt;{{ #viki:pageTitles=First Page Title, Second Page Title,…|width=width|height=height|delimiter=delimiter }}&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

'''Parameters'''
* ''pageTitles'': a list of wiki pages (given by title) to comprise the initial graph (default: the current page)
* ''width'': the desired width (in pixels) of the graph (default: 1200)
* ''height'': the desired height of the graph (default: 600)
* ''delimiter'': the desired delimiter that separates between pageTitles (default: ,)

====VIKI Plugin System====
VIKI is designed to be extensible, with a built-in hook system. Developers can write MediaWiki extensions which serve as plugins to the core VIKI architecture to enhance or modify the VIKI graph behavior. Details about the plugin structure can be found at [[VIKI Plugin Structure|this page]]. Two VIKI plugins enhance functionality and/or provide compatibility support for other MediaWiki and Semantic MediaWiki extensions: 
* [[VIKI Semantic Title]] extension provides support for pages using the [http://www.mediawiki.org/wiki/Extension:SemanticTitle Semantic Title] extension
* [[VIKI Title Icon]] extension provides enhanced functionality for pages using the [[Title Icon]] extension

{{Download|http://www.mediawiki.org/wiki/Extension:VIKI}}
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>75fb38089784560678141bc7b8f13551e4371702</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>VIKI Semantic Title</title>
  <ns>0</ns>
  <id>224</id>
  <revision>
    <id>507</id>
    <parentid>506</parentid>
    <timestamp>2016-02-14T19:09:56Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1187" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
&lt;div class="row"&gt;&lt;div class="large-12 columns"&gt;
====Description====
VIKI Semantic Title is an extension to the VIKI extension to handle pages which use semantic page naming. In semantic page naming, the name of a page is not a human-readable title, but rather something of a systematic format (e.g. "Item:1"), and the title of the page is set via a semantic property. Because VikiJS shows page titles for nodes, this extension ensures that the proper page display title is used rather than the systematic title.

See also the [http://www.mediawiki.org/wiki/Extension:SemanticTitle SemanticTitle] extension for more details on semantic page naming.

The citation pages used to demonstrate Semantic Rating were constructed using Semantic Titles. Instead of displaying node names using actual page names such as Item:1, Item:2, etc., the semantic property [[Property:Full Title]] as the semantic page title.
{| style="background:#ADDFFF;"
|{{#viki:pageTitles=Semantic Rating|width=900|height=600}}
|}&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:VikiSemanticTitle}}

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon=VIKI.png}}
[[Category:Page]]</text>
    <sha1>350a8ef4dd8b108abaf53656e562a3a68a8b7321</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>VIKI Title Icon</title>
  <ns>0</ns>
  <id>225</id>
  <revision>
    <id>509</id>
    <parentid>508</parentid>
    <timestamp>2016-02-14T19:09:56Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="588" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
&lt;div class="row"&gt;&lt;div class="large-12 columns"&gt;
====Description====
VIKI Title Icon is an extension to the VIKI extension which adds support for [[Title Icon]]. If a page has a title icon, the title icon will render as the node logo for that page in place of its wiki logo. The VIKI graph below uses the Title Icon property for its the nodes.
{| style="background:#ADDFFF;"
|{{#viki:pageTitles=Title Icon|width=900|height=600}}
|}&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:VikiTitleIcon}}
{{#set:Title Icon=VIKI.png}}
[[Category:Page]]</text>
    <sha1>5079e1f795833e0286d585a273c84489a998ca24</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Hierarchy Builder</title>
  <ns>0</ns>
  <id>226</id>
  <revision>
    <id>511</id>
    <parentid>510</parentid>
    <timestamp>2016-02-14T19:09:56Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1219" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
====Description====
&lt;div class="row" &gt;&lt;div class="large-7 columns"&gt;The Hierarchy Builder extension allows authors to create hierarchies as bullets in a page, use checkboxes to select hierarchical elements from a form, create and edit hierarchies using drag and drop, query and display the hierarchy results. The Table of Contents for this wiki is used as the hierarchy for many of the examples of the use the extension below. This page provides working examples of how to create and display hierarchies, use checkboxes to select hierarchical elements from a form, create and edit hierarchies using drag and drop. The next page provides working examples of how to [[Hierarchy Querying |query hierarchies]]. For download and installation instructions, see [http://www.mediawiki.org/wiki/Extension:HierarchyBuilder HierarchyBuilder].&lt;/div&gt;
&lt;div class="large-5 columns" style="font-size:80%;"&gt;
{{#hierarchySubtree:Gestalt Wiki Framework Extensions|Table of Contents|Hierarchy Data|displaynameproperty=Name|showroot}}
&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:HierarchyBuilder}}
__NOTOC__
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>035eb613b3bbaa82b13c1b63f3fbcf2c2d23c8de</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Creating</title>
  <ns>0</ns>
  <id>227</id>
  <revision>
    <id>513</id>
    <parentid>512</parentid>
    <timestamp>2016-02-14T19:09:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3660" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
====Description====
&lt;div class="row"&gt;&lt;div class="large-6 columns"&gt;
This page describes how to create hierarchies using the &lt;nowiki&gt;&lt;hierarchy&gt;&lt;/nowiki&gt; tag. There are three optional attributes the &lt;nowiki&gt;&lt;hierarchy&gt;&lt;/nowiki&gt; tag takes: ''collapsed, displaynameproperty'', and ''autonumbered''. The grey boxes on the left show the wikitext code. The blue boxes on the right show the extension in action.__TOC__&lt;/div&gt;&lt;div class="large-6 columns"&gt;{{Legend}}&lt;/div&gt;&lt;/div&gt;
====Usage: Hierarchy Expanded====
This is an example of the use of the &lt;nowiki&gt;&lt;hierarchy&gt;&lt;/nowiki&gt; tag without any attributes.
&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
&lt;hierarchy&gt;
*[[Gestalt Wiki Framework]]
**[[Hierarchy Builder]]
**[[Semantic Rating]]
**[[Title Icon]]
**[[Network Graph]]
&lt;/hierarchy&gt;
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|&lt;hierarchy&gt;
*[[Gestalt Wiki Framework]]
**[[Hierarchy Builder]]
**[[Semantic Rating]]
**[[Title Icon]]
**[[Network Graph]]
&lt;/hierarchy&gt;
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Hierarchy Collapsed====
To show a hierarchy collapsed, add the attribute ''collapsed.''
&lt;div class="row"&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:80%;"&gt;
&lt;pre&gt;
&lt;hierarchy collapsed&gt;
*[[Gestalt Wiki Framework]]
**[[Hierarchy Builder]]
**[[Semantic Rating]]
**[[Title Icon]]
**[[Network Graph]]
&lt;/hierarchy&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:90%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|&lt;hierarchy collapsed&gt;
*[[Gestalt Wiki Framework]]
**[[Hierarchy Builder]]
**[[Semantic Rating]]
**[[Title Icon]]
**[[Network Graph]]
&lt;/hierarchy&gt;
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Hierarchy With Different Display Names====
&lt;p&gt;To display a different page name, set the attribute ''displaynameproperty'' to a different property name. The citations in this wiki use the following page naming: Item:1..n. Each page in Category:Items has a property Short_Title.&lt;/p&gt;
&lt;div class="row"&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:80%;"&gt;
&lt;pre&gt;
&lt;hierarchy displaynameproperty=Short_Title&gt;
*[[Enterprise Wiki Articles]]
**[[Item:1]]
**[[Item:4]]
**[[Item:2]]
**[[Item:3]]
**[[Item:5]]
&lt;/hierarchy&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:90%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|&lt;hierarchy displaynameproperty=Short_Title&gt;
*[[Enterprise Wiki Articles]]
**[[Item:1]]
**[[Item:4]]
**[[Item:2]]
**[[Item:3]]
**[[Item:5]]
&lt;/hierarchy&gt;
|}&lt;/div&gt;&lt;/div&gt;
{{New Paragraph}}
====Usage: Hierarchy With Different Display Names and Element Numbers====
&lt;p&gt;Building on the example above, add the attribute ''numbered.''&lt;/p&gt;
&lt;div class="row"&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:80%;"&gt;
&lt;pre&gt;
&lt;hierarchy numbered displaynameproperty=Short_Title &gt;
*[[Enterprise Wiki Articles]]
**[[Item:1]]
**[[Item:4]]
**[[Item:2]]
**[[Item:3]]
**[[Item:5]]
&lt;/hierarchy&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:90%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|&lt;hierarchy numbered displaynameproperty=Short_Title &gt;
*[[Enterprise Wiki Articles]]
**[[Item:1]]
**[[Item:4]]
**[[Item:2]]
**[[Item:3]]
**[[Item:5]]
&lt;/hierarchy&gt;
|}&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:HierarchyBuilder}}

{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>a7fbc000af556b1199050a7ec277b170fba894f7</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Talk:Selecting</title>
  <ns>1</ns>
  <id>228</id>
  <revision>
    <id>515</id>
    <parentid>514</parentid>
    <timestamp>2016-02-14T19:09:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">[[Category:Page]]</text>
    <sha1>6d68468a3db13903a05fdaee202205a53a76ce07</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Selecting</title>
  <ns>0</ns>
  <id>229</id>
  <revision>
    <id>517</id>
    <parentid>516</parentid>
    <timestamp>2016-02-14T19:09:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1700" xml:space="preserve">{{Breadcrumb}}__NOEDITSECTION__
==== Description ====
&lt;div class="row"&gt;&lt;div class="large-6 columns"&gt;
The hierarchySelect Semantic Form input type allows users to select a subset of pages from a hierarchy within a form to populate a multi-valued property of type Page. &lt;/div&gt; &lt;div class="large-6 columns"&gt;[[Image:ExtensionUsage.png|400px]]&lt;br&gt;Screenshot of Form:Survey&lt;/div&gt; &lt;/div&gt; 
==== Usage ====
The hierarchySelect input type can be seen in action by clicking on the "Click this Link" link. The name of the property that stores the hierarchy [[Property:Hierarchy Data]] and the page on which that property is set, [[Gestalt Extensions]], must be provided in the form in order to be able to locate the hierarchy. 

&lt;div class="row" &gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;&lt;includeonly&gt;
{{{info|page name=Survey Response_&lt;unique number;start=001&gt;|create title=Survey|edit title=Survey}}}
{{{for template|Survey}}}
{| class="formtable"
! Which extensions have you used?
| {{{field|Extensions|input type=hierarchySelect|pagename=Gestalt Extensions|propertyname=Hierarchy Data|list}}}
|}
{{{end template}}}
{{{standard input|save}}}  {{{standard input|cancel}}}
&lt;/includeonly&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;div class="large-6 columns" style="font-size:90%;"&gt;
{| style="border: solid 1px #D0D0D0;"
|{{#formlink:form=Survey|link text=Click this link|link type=link}}
|-
|Click on these pages and then open them using "Edit" dropdown action{{#ask: [[Category:Responses]]
|?Extensions
|format=table
}}
|}&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:HierarchyBuilder}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>6567a171190e2f06369774a108e0cde162575803</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Querying</title>
  <ns>0</ns>
  <id>230</id>
  <revision>
    <id>519</id>
    <parentid>518</parentid>
    <timestamp>2016-02-14T19:09:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13244" xml:space="preserve">{{Breadcrumb}} __NOEDITSECTION__
====Description====
&lt;div class="row"&gt;&lt;div class="large-6 columns"&gt; This page describes how to use Hierarchy Builder's parser functions to query the elements in a hierarchy. __TOC__&lt;/div&gt;
&lt;div class="large-6 columns"&gt;{{Legend}}&lt;/div&gt;&lt;/div&gt;

====Usage: Hierarchy Breadcrumb====
The ''hierarchyBreadcrumb'' parser function can be used to display a hierarchy breadcrumb bar at the top of a page including the previous row, hierarchical parent row, and next row within the hierarchy.

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| current page
| Text
| ''
| The current page within the hierarchy for which the breadcrumb should be returned.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be used.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|-
| displaynameproperty
| Text
| ''
| The property containing a page's display name if using semantic page names.
|}

The parser function invocation below displays the breadcrumb for the page ''{{FULLPAGENAME}}'' within the hierarchy stored in property ''Hierarchy Data'' on the page ''Table of Contents'' using the semantic page names stored within the property ''Name'' on each page. The bar might contain the row that immediately precedes ''{{FULLPAGENAME}}'', immediately succeeds ''{{FULLPAGENAME}}'', and the hierarchical parent of ''{{FULLPAGENAME}}'' within the hierarchy on the page ''Table of Contents''.

&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#hierarchyBreadcrumb:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data|Name}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchyBreadcrumb:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data|Name}}
|}&lt;/div&gt;&lt;/div&gt;

====Usage: Hierarchy Children====
The ''hierarchyChildren'' parser function can be used to retrieve the immediate hierarchical children of a given page from a hierarchy on a specified page. 

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| page name
| Text
| ''
| The target page within the hierarchy for which the immediate children should be returned. If left empty then all root level rows will be returned instead.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be searched.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|-
| template
| Text
| ''
| The name of a template with which to display the printouts.
|-
| introtemplate
| Text
| ''
| The name of a template to display before the results if there are any.
|-
| outrotemplate
| Text
| ''
| The name of a template to display after the results if there are any.
|-
| link
| 'none' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify whether or not to display results as links if there are any results.
|-
| sep
| Text
| ','
| Used to specify the separator for returned values.
|}

The parser function takes the following three mandatory arguments in order: page name, hierarchy page, and hierarchy property. There are also the following optional arguments: ''sep'', ''template'', ''introtemplate'', ''outrotemplate'', and ''link''. The ''sep'' argument is used to specify the separator for returned values. The argument ''template'' is the name of a template with which to display the printouts. The ''introtemplate'' argument is the name of a template to display before the results if there are any. The ''outrotemplate'' argument is the name of a template to display after the results if there are any. The argument ''link'' is used to specify whether or not to display results as links if there are any results. The value of the ''link'' argument can either be empty or ''none''. By default, ''link'' is enabled.

The parser function invocation below displays the template ''Y'' followed by the immediate children of the page ''Table of Contents'' in the hierarchy stored in the property ''hierarchy property'' on the page ''hierarchy page'' after applying the template ''X'' to each result, followed by the template ''Z''.

&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#hierarchyChildren:Hierarchy Builder|Table of Contents|Hierarchy Data|template=X|introtemplate=Y|outrotemplate=Z|link=none}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchyChildren:Hierarchy Builder|Table of Contents|Hierarchy Data|template=X|introtemplate=Y|outrotemplate=Z|link=none}}
|}&lt;/div&gt;&lt;/div&gt;
====Usage: Hierarchy Parent====
The ''hierarchyParent'' parser function is used to retrieve the hierarchical parent of a given page from a hierarchy on a specified page. 

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| page name
| Text
| Mandatory
| The target page within the hierarchy for which the immediate hierarchical parent should be returned.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be searched.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|-
| template
| Text
| ''
| The name of a template with which to display the printouts.
|-
| introtemplate
| Text
| ''
| The name of a template to display before the results if there are any.
|-
| outrotemplate
| Text
| ''
| The name of a template to display after the results if there are any.
|-
| link
| 'none' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify whether or not to display results as links if there are any results.
|-
| sep
| Text
| ','
| Used to specify the separator for returned values.
|}

The parser function take the following three mandatory arguments in order: page name, hierarchy page, and hierarchy property. Additionally, there are also the following optional arguments: ''template'', ''introtemplate'', ''outrotemplate'', and ''link''. Each of these arguments behaves the same as they do for the ''hierarchyChildren ''parser function above. The argument ''template'' is the name of a template with which to display the printouts. The ''introtemplate'' argument is the name of a template to display before the results if there are any. The ''outrotemplate'' argument is the name of a template to display after the results if there are any. The argument ''link'' is used to specify whether or not to display results as links if there are any results. The value of the ''link'' argument can either be empty or ''none''. By default, ''link'' is enabled.

The parser function invocation below displays the hierarchical parent row of ''{{FULLPAGENAME}}'' within the hierarchy stored in property ''hierarchy property'' on the page ''hierarchy page name'' rendered as a hyperlink.
&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#hierarchyParent:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data|link=none}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchyParent:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data|link=none}}
|}&lt;/div&gt;&lt;/div&gt;
====Usage: Hierarchy Section Number====
The ''hierarchySectionNumber'' parser function is used to automatically compute a given page's section number within a particular hierarchy on a specified page. 

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| page name
| Text
| Mandatory
| The target page within the hierarchy for which the section number should be returned.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be searched.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|}

The parser function takes three mandatory arguments in order: page name, hierarchy page, and hierarchy property. The parser function invocation below give the section number of the page ''{{FULLPAGENAME}}'' within the hierarchy in property ''Hierarchy Data'' on the page ''[[Table of Contents]]''.

&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#hierarchySectionNumber:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchySectionNumber:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data}}
|}&lt;/div&gt;&lt;/div&gt;

====Usage: Hierarchy Subtree====
The ''hierarchySubtree'' parser function is used to render the subtree rooted at a given node within a specified hierarchy. 

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| root node
| Text
| Mandatory
| The node that forms the root of the desired subtree.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be searched.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|-
| format
| 'ul' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify the display formatting of the returned subtree. Either bulleted or hierarchical.
|-
| displaynameproperty
| Text
| ''
| The name of the property containing a page's display name. Used to support semantic page names.
|-
| showroot
| 'showroot' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify that the subtree's root should also be displayed.
|-
| collapsed
| 'collapsed' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify that the subtree should be initialized in collapsed mode.
|}

The parser function takes three mandatory arguments in order: root node, hierarchy page, and hierarchy property. If format is given as 'ul' then the subtree will be rendered as a bulleted list. Otherwise, the subtree is rendered by default as a hierarchy. If 'showroot' is given then the root of the subree will be rendered as a part of the result. By default the root of the subtree is hidden in the display. If 'collapsed' is given then the subtree will be initialized in collapsed mode. By default the subtree is not rendered in collapsed mode.

The parser function invocation below renders the subtree rooted at "Hierarchy Builder" within the hierarchy in property ''Hierarchy Data'' on the page ''Table of Contents'' as a bulleted list.

&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:70%;"&gt;
&lt;pre&gt;
{{#hierarchySubtree:Hierarchy Builder|Table of Contents|Hierarchy Data}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchySubtree:Hierarchy Builder|Table of Contents|Hierarchy Data}}
|}&lt;/div&gt;&lt;/div&gt;
====Usage: Hierarchy Selected====
The ''hierarchySelected'' parser function is used to find and render the minimum spanning tree that contains specified rows within a hierarchy in addition to the root node of the specified hierarchy. The rendered minimum spanning tree will show each selected node with a checked box.

The parameters are given in the table below:
{| class="wikitable"
! Parameter
! Type
! Default
! Description
|-
| selected pages
| Text
| Mandatory
| A comma delimited list of rows that are selected within a hierarchy.
|-
| hierarchy page
| Text
| Mandatory
| The page containing the hierarchy to be searched.
|-
| hierarchy property
| Text
| Mandatory
| The name of the semantic property containing the hierarchy data.
|-
| display mode
| 'collapsed' / &lt;i&gt;empty&lt;/i&gt;
| ''
| Used to specify whether the rendered minimum spanning tree should be initialized in collapsed mode or not.
|}

The parser function takes three mandatory arguments in order: selected pages, hierarchy page, and hierarchy property. If the display mode is given as 'collapsed' then the minimum spanning tree will be initialized in collapsed display mode. The parser function invocation below renders the minimum spanning tree in collapsed mode of the hierarchy in property ''hierarchy property'' on the page ''hierarchy page name'' which contained the hierarchy root and each of the listed page names so that the listed page names would be marked as "checked".

&lt;div class="row" width=100%&gt;&lt;div class="large-5 columns" style="margin-left:20px;border: solid 1px #D0D0D0;background: #F0F0F0;font-size:60%;"&gt;
&lt;pre&gt;
{{#hierarchySelected:Creating,Editing,Selecting,Querying|Table of Contents|Hierarchy Data|collapsed}}
&lt;/pre&gt;&lt;/div&gt;&lt;div class="large-6 columns" style="font-size:80%;"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchySelected:Creating,Editing,Selecting,Querying|Table of Contents|Hierarchy Data|collapsed}}
|}&lt;/div&gt;&lt;/div&gt;
{{Download|http://www.mediawiki.org/wiki/Extension:HierarchyBuilder}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>2632ea1e3c5b8b961b5864997ef710118c562252</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>About</title>
  <ns>0</ns>
  <id>231</id>
  <revision>
    <id>521</id>
    <parentid>520</parentid>
    <timestamp>2016-02-14T19:09:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1641" xml:space="preserve">{{Breadcrumb}}
&lt;div class="row" &gt;&lt;div class="large-6 columns"&gt;GWF wikis are hosted on virtual machines built on a LAMP stack. LAMP includes:
*{{Elink|http://en.wikipedia.org/wiki/Linux|Linux}} operating system,  
*{{Elink|http://en.wikipedia.org/wiki/Apache_HTTP_Server|Apache HTTP Server}},  
*{{Elink|http://en.wikipedia.org/wiki/MySQL|MySQL}} relational database management system, and
*{{Elink|http://en.wikipedia.org/wiki/PHP|PHP}} programming language. 
{{New Paragraph}}
Wiki software from {{Elink|http://www.mediawiki.org/wiki/MediaWiki|MediaWiki}} and {{Elink|https://semantic-mediawiki.org|Semantic MediaWiki}} is used. MediaWiki is used to run {{Elink|https://en.wikipedia.org/|Wikipedia}} and is used by {{Elink|https://wikiapiary.com/wiki/Main_Page|over 25,000}} sites.  Semantic MediaWiki is used by {{Elink|https://wikiapiary.com/wiki/Main_Page|over 1,300 sites}} to annotate page content with properties that can be queried and visualized. Many GWF extensions, some of which are MediaWiki extensions and others which are Semantic MediaWiki extensions have been contributed to the {{Elink|http://www.mediawiki.org/wiki/Category:Extensions_by_MITRE|open source community}}. All the software components used to build this GWF wiki are automatically listed on the [[Special:Version|version page]]. &lt;/div&gt;
&lt;div class="large-6 columns"&gt;[[Image:MGF.png|600px]]&lt;br&gt;GWF Stack&lt;/div&gt;&lt;/div&gt;
To learn more about Gestalt Wiki Framework, see our [[Publications|publications]], [[Team|team]], [[MITRE|enterprise]], and [[Contact |contact information]] pages.

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>cdf4b93b326c5b1d417512739184e705d57cd892</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Blogs and Presentations</title>
  <ns>0</ns>
  <id>232</id>
  <revision>
    <id>523</id>
    <parentid>522</parentid>
    <timestamp>2016-02-14T19:09:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="540" xml:space="preserve">__NOEDITSECTION__
====Blogs====
[[Image:BlogOrigins.png|200px|link=https://publish.mitre.org/kde/2015/03/26/gestalt-wikis-at-mitre-march-2015]] [https://publish.mitre.org/kde/2015/03/26/gestalt-wikis-at-mitre-march-2015/ Gestalt Wikis at MITRE Knowledge Driven Enterprise Blog]
----
====Presentations====
{{#ask: [[Category:Presentations]] |limit=100
|?Responsive Presentation=
|?Has date=Date
|sort=Has date
|order=descending
|mainlabel=-
|format=table
}}

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon=Presentations.png}}
[[Category:Page]]</text>
    <sha1>72a0948a6ecfd70509d7ac36ad1520340cc17141</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Team</title>
  <ns>0</ns>
  <id>233</id>
  <revision>
    <id>525</id>
    <parentid>524</parentid>
    <timestamp>2016-02-14T19:09:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="189" xml:space="preserve">{{#ask: [[Category:Users]][[Linkedin-url::+]]
|?Linkedin-url=
|?Name=
|format=template
|template=Gallery
}}
{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>9b40ff5b461351505cc3046dee205ad0f0f54985</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Nested Tabs</title>
  <ns>0</ns>
  <id>234</id>
  <revision>
    <id>527</id>
    <parentid>526</parentid>
    <timestamp>2016-02-14T19:10:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2262" xml:space="preserve">&lt;div style="font-size:80%;"&gt;
&lt;div class="section-container auto"  data-section&gt;
&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Background&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Introduction|{{:Gestalt Wiki Framework}}}}
{{Tab||Background|{{:Background}}}}
{{Tab||Enterprise Collaboration|{{:Enterprise Collaboration}}}}
{{Tab||Content Networks|{{:Content Networks}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Wiki Design&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Wiki Development&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Configure a Wiki|[[Image:UnderConstruction.png|50px]]}} 
{{Tab||Create Classes|[[Image:UnderConstruction.png|50px]]}}  
{{Tab||Create Queries and Visualizations|[[Image:UnderConstruction.png|50px]]}}  
{{Tab||Patterns|[[Image:UnderConstruction.png|50px]]}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Gestalt Wiki Framework Extensions&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Introduction|{{:Gestalt Wiki Framework Extensions}}}}
{{Tab||Title Icon|{{:Title Icon}}}} 
{{Tab||Semantic Rating|{{:Semantic Rating}}}}  
{{Tab||VIKI Network Graph|{{:VIKI Network Graph}}}}  
{{Tab||VIKI Semantic Title|{{:VIKI Semantic Title}}}}
{{Tab||VIKI Title Icon|{{:VIKI Title Icon}}}}
{{Tab||Hierarchy Builder|{{:Hierarchy Builder}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;About&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Publications|{{:Publications}}}}
{{Tab||Team|{{:Team}}}}
{{Tab||MITRE|{{:MITRE}}}}
{{Tab||Contact|{{:Contact}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;
&lt;/div&gt;
__NOTOC__
 {{#set:Hide Title Icon=all}}</text>
    <sha1>c8a0aaf4f28e87f141edba6963927368fddb3de0</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>MITRE</title>
  <ns>0</ns>
  <id>235</id>
  <revision>
    <id>529</id>
    <parentid>528</parentid>
    <timestamp>2016-02-14T19:10:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="841" xml:space="preserve">&lt;div class="row" &gt;&lt;div class="large-8 columns"&gt;Our team works at MITRE, a not-for-profit organization that operates research and development centers sponsored by the federal government. MITRE operates FFRDCs—federally funded research and development centers—which are unique organizations that assist the United States government with:

* Scientific research and analysis
* Development and acquisition
* Systems engineering and integration

MITRE also has an independent research program that explores new and expanded uses of technologies to solve customers' problems. For more information about MITRE, visit [http://www.mitre.org mitre.org].&lt;/div&gt;&lt;div class="large-4 columns"&gt;[[Image:MITRE1.png|500px|MITRE McLean, VA]]&lt;br&gt;MITRE, McLean, VA&lt;/div&gt;&lt;/div&gt;

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>102774df2e2047838096c6b4ab061e543b226a6e</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Contact</title>
  <ns>0</ns>
  <id>236</id>
  <revision>
    <id>531</id>
    <parentid>530</parentid>
    <timestamp>2016-02-14T19:10:01Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="330" xml:space="preserve">If you are interested in 

*Learning more about the Gestalt Wiki Framework,
*How enterprise wikis can help government agencies build and share knowledge, or
*Providing us feedback on this site,

Please send email to: [mailto:bclemente@mitre.org Gestalt Wiki Framework team].

{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:Page]]</text>
    <sha1>73e6ba07c11f1e0839bd9e2a41939258ff0912e9</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Vision</title>
  <ns>0</ns>
  <id>237</id>
  <revision>
    <id>533</id>
    <parentid>532</parentid>
    <timestamp>2016-02-14T19:10:04Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">[[Category:Page]]</text>
    <sha1>6d68468a3db13903a05fdaee202205a53a76ce07</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Wiki Federation</title>
  <ns>0</ns>
  <id>238</id>
  <revision>
    <id>535</id>
    <parentid>534</parentid>
    <timestamp>2016-02-14T19:10:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">[[Category:Page]]</text>
    <sha1>6d68468a3db13903a05fdaee202205a53a76ce07</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Nested Tabs 2</title>
  <ns>0</ns>
  <id>239</id>
  <revision>
    <id>537</id>
    <parentid>536</parentid>
    <timestamp>2016-02-14T19:10:06Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2262" xml:space="preserve">&lt;div style="font-size:80%;"&gt;
&lt;div class="section-container auto"  data-section&gt;
&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Background&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Introduction|{{:Gestalt Wiki Framework}}}}
{{Tab||Background|{{:Background}}}}
{{Tab||Enterprise Collaboration|{{:Enterprise Collaboration}}}}
{{Tab||Content Networks|{{:Content Networks}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Wiki Design&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Wiki Development&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Configure a Wiki|[[Image:UnderConstruction.png|50px]]}} 
{{Tab||Create Classes|[[Image:UnderConstruction.png|50px]]}}  
{{Tab||Create Queries and Visualizations|[[Image:UnderConstruction.png|50px]]}}  
{{Tab||Patterns|[[Image:UnderConstruction.png|50px]]}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;Gestalt Wiki Framework Extensions&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Introduction|{{:Gestalt Wiki Framework Extensions}}}}
{{Tab||Title Icon|{{:Title Icon}}}} 
{{Tab||Semantic Rating|{{:Semantic Rating}}}}  
{{Tab||VIKI Network Graph|{{:VIKI Network Graph}}}}  
{{Tab||VIKI Semantic Title|{{:VIKI Semantic Title}}}}
{{Tab||VIKI Title Icon|{{:VIKI Title Icon}}}}
{{Tab||Hierarchy Builder|{{:Hierarchy Builder}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;

&lt;div class="section"&gt;
&lt;p class="title" style="font-size:small;" data-section-title&gt;About&lt;/p&gt;
&lt;div class="content" data-section-content&gt;
&lt;div class="section-container auto" style="font-size:small;" data-section&gt;
{{Tab||Publications|{{:Publications}}}}
{{Tab||Team|{{:Team}}}}
{{Tab||MITRE|{{:MITRE}}}}
{{Tab||Contact|{{:Contact}}}}
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;
&lt;/div&gt;
__NOTOC__
 {{#set:Hide Title Icon=all}}</text>
    <sha1>c8a0aaf4f28e87f141edba6963927368fddb3de0</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Abstract</title>
  <ns>102</ns>
  <id>240</id>
  <revision>
    <id>539</id>
    <parentid>538</parentid>
    <timestamp>2016-02-14T19:10:06Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Author</title>
  <ns>102</ns>
  <id>241</id>
  <revision>
    <id>541</id>
    <parentid>540</parentid>
    <timestamp>2016-02-14T19:10:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Average Rating Stars</title>
  <ns>102</ns>
  <id>242</id>
  <revision>
    <id>543</id>
    <parentid>542</parentid>
    <timestamp>2016-02-14T19:10:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Citation</title>
  <ns>102</ns>
  <id>243</id>
  <revision>
    <id>545</id>
    <parentid>544</parentid>
    <timestamp>2016-02-14T19:10:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:DOI</title>
  <ns>102</ns>
  <id>244</id>
  <revision>
    <id>547</id>
    <parentid>546</parentid>
    <timestamp>2016-02-14T19:10:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47" xml:space="preserve">[[Has type::Text]]
[[Category:Framework Pages]]</text>
    <sha1>793928a9cf583921e396749ebc4a0c88e2d40746</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Five Star Review Count</title>
  <ns>102</ns>
  <id>245</id>
  <revision>
    <id>549</id>
    <parentid>548</parentid>
    <timestamp>2016-02-14T19:10:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Four Star Review Count</title>
  <ns>102</ns>
  <id>246</id>
  <revision>
    <id>551</id>
    <parentid>550</parentid>
    <timestamp>2016-02-14T19:10:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Full Title</title>
  <ns>102</ns>
  <id>49</id>
  <revision>
    <id>553</id>
    <parentid>73</parentid>
    <timestamp>2016-02-14T19:10:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Item</title>
  <ns>102</ns>
  <id>247</id>
  <revision>
    <id>555</id>
    <parentid>554</parentid>
    <timestamp>2016-02-14T19:10:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Page]].
[[Category:Framework Pages]]</text>
    <sha1>35138e263c93432ca7be64f2ecdb8edf070d91e5</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Item Type</title>
  <ns>102</ns>
  <id>59</id>
  <revision>
    <id>557</id>
    <parentid>124</parentid>
    <timestamp>2016-02-14T19:10:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="492" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]

[[Allows value::article]]
[[Allows value::book]]
[[Allows value::booklet]]
[[Allows value::conference]]
[[Allows value::inbook]]
[[Allows value::incollection]]
[[Allows value::inproceedings]]
[[Allows value::manual]]
[[Allows value::mastersthesis]]
[[Allows value::misc]]
[[Allows value::phdthesis]]
[[Allows value::proceedings]]
[[Allows value::standard]]
[[Allows value::techreport]]
[[Allows value::unpublished]]</text>
    <sha1>abcd7257bbc4f8f15fdc7663c0b0f654f7b111a9</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Item Type Image</title>
  <ns>102</ns>
  <id>248</id>
  <revision>
    <id>559</id>
    <parentid>558</parentid>
    <timestamp>2016-02-14T19:10:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Keyword Links</title>
  <ns>102</ns>
  <id>249</id>
  <revision>
    <id>561</id>
    <parentid>560</parentid>
    <timestamp>2016-02-14T19:10:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:One Star Review Count</title>
  <ns>102</ns>
  <id>250</id>
  <revision>
    <id>563</id>
    <parentid>562</parentid>
    <timestamp>2016-02-14T19:10:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Publisher</title>
  <ns>102</ns>
  <id>251</id>
  <revision>
    <id>565</id>
    <parentid>564</parentid>
    <timestamp>2016-02-14T19:10:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Rating</title>
  <ns>102</ns>
  <id>252</id>
  <revision>
    <id>567</id>
    <parentid>566</parentid>
    <timestamp>2016-02-14T19:10:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">This is a property of type [[Has type::Number]].
[[Category:Framework Pages]]</text>
    <sha1>58a20cb7fe63db16b7ea0e1b733e8a5bf9e55ac8</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Review Title</title>
  <ns>102</ns>
  <id>253</id>
  <revision>
    <id>569</id>
    <parentid>568</parentid>
    <timestamp>2016-02-14T19:10:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">This is a property of type [[Has type::String]].
[[Category:Framework Pages]]</text>
    <sha1>f250aed81da8f3df5d26714a915e6cee93cd086e</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Reviewer</title>
  <ns>102</ns>
  <id>254</id>
  <revision>
    <id>571</id>
    <parentid>570</parentid>
    <timestamp>2016-02-14T19:10:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Page]].
[[Category:Framework Pages]]</text>
    <sha1>35138e263c93432ca7be64f2ecdb8edf070d91e5</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Sorting Title</title>
  <ns>102</ns>
  <id>255</id>
  <revision>
    <id>573</id>
    <parentid>572</parentid>
    <timestamp>2016-02-14T19:10:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">This is a property of type [[Has type::String]].
[[Category:Framework Pages]]</text>
    <sha1>f250aed81da8f3df5d26714a915e6cee93cd086e</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Three Star Review Count</title>
  <ns>102</ns>
  <id>256</id>
  <revision>
    <id>575</id>
    <parentid>574</parentid>
    <timestamp>2016-02-14T19:10:12Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Two Star Review Count</title>
  <ns>102</ns>
  <id>257</id>
  <revision>
    <id>577</id>
    <parentid>576</parentid>
    <timestamp>2016-02-14T19:10:12Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Volume</title>
  <ns>102</ns>
  <id>258</id>
  <revision>
    <id>579</id>
    <parentid>578</parentid>
    <timestamp>2016-02-14T19:10:12Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Year</title>
  <ns>102</ns>
  <id>259</id>
  <revision>
    <id>581</id>
    <parentid>580</parentid>
    <timestamp>2016-02-14T19:10:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">This is a property of type [[Has type::String]].
[[Category:Framework Pages]]</text>
    <sha1>f250aed81da8f3df5d26714a915e6cee93cd086e</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Template:Presentation</title>
  <ns>10</ns>
  <id>260</id>
  <revision>
    <id>583</id>
    <parentid>582</parentid>
    <timestamp>2016-02-14T19:10:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="749" xml:space="preserve">&lt;includeonly&gt;{| class="wikitable"
! Description
| {{{Description|}}}
|-
! Authors
|  {{#arraymap:{{{Authors|}}}|,|@@@@|[[User:@@@@]]}} 
|-
! Date
| {{{Has date|}}}
|}
{{#if:{{{File|}}}|
{{#widget:Iframe
|url={{filepath:{{{File}}}}}
|width=900
|height=800
|border=0
}}}}
&lt;div style="display:none;"&gt;
{{#set:Name={{{Name|}}}}}
{{#set:Description={{{Description|}}}}}
{{#arraymap:{{{Authors|}}}|,|@@@@|{{#set:Authors=@@@@}}}} 
{{#set:Has date={{{Has date|}}}}}
{{#set:Responsive Presentation=&lt;div class="row"&gt;&lt;div class="large-2 columns"&gt;[[Image:{{{Thumbnail}}}|200px|link={{PAGENAME}}]]&lt;/div&gt;&lt;div class="large-10 columns"&gt;[[{{PAGENAME}}]]&lt;/div&gt;&lt;/div&gt;}}
[[Category:Presentations]]
&lt;/div&gt;
&lt;/includeonly&gt;&lt;noinclude&gt;[[Category:Framework Pages]]&lt;/noinclude&gt;</text>
    <sha1>2a607dea97787ff2a039fecffd8ded441ff5e27c</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Form:Presentation</title>
  <ns>106</ns>
  <id>261</id>
  <revision>
    <id>585</id>
    <parentid>584</parentid>
    <timestamp>2016-02-14T19:10:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="411" xml:space="preserve">&lt;includeonly&gt;
{{{for template|Presentation}}}
{| class="formtable"
! Description
| {{{field|Description}}}
|-
! Authors:
| {{{field|Authors}}}
|-
! Date
| {{{field|Has date}}}
|-
! Thumbnail
| {{{field|Thumbnail|uploadable}}}
|-
! File
| {{{field|File|uploadable}}}
|}
{{{end template}}}

{{{standard input|save}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;
&lt;noinclude&gt;
[[Category:Framework Pages]]
&lt;/noinclude&gt;</text>
    <sha1>aec2aff2b37674cc42c9dc0386c81e1dbab4506c</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Has date</title>
  <ns>102</ns>
  <id>163</id>
  <revision>
    <id>587</id>
    <parentid>373</parentid>
    <timestamp>2016-02-14T19:10:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Date]].</text>
    <sha1>5263c8921631f25051f416df19a72490a588561e</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Keywords</title>
  <ns>0</ns>
  <id>262</id>
  <revision>
    <id>589</id>
    <parentid>588</parentid>
    <timestamp>2016-02-14T19:10:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="483" xml:space="preserve">&lt;div style="display:none;"&gt;
{{#vardefine:keyword|{{lc:{{#urldecode:{{#urlget:keyword}}}}}}}} 
&lt;/div&gt;
{{#ask:[[Category:Research Proposals]][[Keywords::{{#var:keyword}}]]
|?Average Rating Stars
|?Citation
|mainlabel=-
|headers=hide
|class=citationtable
|limit=50
|searchlabel=
|sort=Average Rating Number
|order=desc
}}

&lt;div style="display:none;"&gt;
{{#set:Dynamic Display=$keyword}}
{{#set:Logo Link=Keywords.png}}
{{DISPLAYTITLE:{{#var:keyword}}}}
[[Category:Framework Pages]]
&lt;/div&gt;</text>
    <sha1>ad18314a82d7b8c5bc77819db0cd653f023cd104</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Property:Keyword</title>
  <ns>102</ns>
  <id>263</id>
  <revision>
    <id>591</id>
    <parentid>590</parentid>
    <timestamp>2016-02-14T19:10:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Text]].
[[Category:Framework Pages]]</text>
    <sha1>f456953c0b52bc8e666e3709beefc9c3e44d970b</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Template:Breadcrumb</title>
  <ns>10</ns>
  <id>264</id>
  <revision>
    <id>593</id>
    <parentid>592</parentid>
    <timestamp>2016-02-14T19:10:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="264" xml:space="preserve">&lt;includeonly&gt;&lt;div class="row"&gt;&lt;div class="large-12 columns" class="hierarchyText"&gt;{{#hierarchyBreadcrumb:{{FULLPAGENAME}}|Table of Contents|Hierarchy Data|Name}}&lt;/div&gt;&lt;/div&gt;
&lt;div class="row"&gt;&lt;div class="large-12 columns"&gt;{{New Paragraph}}&lt;/div&gt;&lt;/div&gt;&lt;/includeonly&gt;</text>
    <sha1>e6bbeffbad3499881227a476c9a39a2b118ee7be</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Template:New Paragraph</title>
  <ns>10</ns>
  <id>62</id>
  <revision>
    <id>595</id>
    <parentid>132</parentid>
    <timestamp>2016-02-14T19:10:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="102" xml:space="preserve">&lt;includeonly&gt;
&lt;div class="np"&gt;&lt;/div&gt;
&lt;/includeonly&gt;&lt;noinclude&gt;[[Category:Framework Pages]]&lt;/noinclude&gt;</text>
    <sha1>4de0b1b5b72807dfd76e4dafde6bab88c4430c85</sha1>
  </revision>
</page>
<page arvcontinue="20160214190954|499">
  <title>Template:RefList</title>
  <ns>10</ns>
  <id>265</id>
  <revision>
    <id>597</id>
    <parentid>596</parentid>
    <timestamp>2016-02-14T19:10:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="92" xml:space="preserve">&lt;includeonly&gt;
'''References'''
&lt;div id="reference-block"&gt;
&lt;references /&gt;&lt;/div&gt;&lt;/includeonly&gt;</text>
    <sha1>26237a1877fd0c09294cb2c9fc083e4a7448c9c3</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>Template:Elink</title>
  <ns>10</ns>
  <id>266</id>
  <revision>
    <id>599</id>
    <parentid>598</parentid>
    <timestamp>2016-02-14T19:10:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="76" xml:space="preserve">&lt;includeonly&gt;&lt;span class="plainlinks"&gt;[{{{1}}} {{{2}}}]&lt;/span&gt;&lt;/includeonly&gt;</text>
    <sha1>d5574cbe6609c35f82ca56241f049a823b7fdfac</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>Template:Legend</title>
  <ns>10</ns>
  <id>267</id>
  <revision>
    <id>601</id>
    <parentid>600</parentid>
    <timestamp>2016-02-14T19:10:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1187" xml:space="preserve">&lt;includeonly&gt;
&lt;div style="border: solid 1px #c0c0c0;"&gt;
&lt;div class="row" style="padding:5px;"&gt;&lt;div class="small-12 columns" style="color:#009933;"&gt;'''Legend'''&lt;/div&gt;&lt;/div&gt;&lt;div  style="padding:5px;font-size:90%;"&gt;&lt;div class="row" style="margin-bottom:-3px;"&gt;&lt;div class="small-3 columns"&gt;Wiki text&lt;/div&gt;&lt;div class="small-9 columns"&gt;
{| style="background: #F0F0F0;"
|&lt;pre&gt;
{{{field|Rating|input type=rating}}}
&lt;/pre&gt;
|}&lt;/div&gt;&lt;/div&gt;
&lt;div class="row"  style="margin-bottom:-3px;"&gt;&lt;div class="small-3 columns"&gt;Live example&lt;/div&gt;&lt;div class="small-9 columns"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#hierarchyBreadcrumb:Querying|Table of Contents|Hierarchy Data|Name}}
|}&lt;/div&gt;&lt;/div&gt;
&lt;div class="row"  style="margin-bottom:-3px;"&gt;&lt;div class="small-3 columns" &gt;Live example&lt;/div&gt;&lt;div class="small-9 columns"&gt;
{| style="border: solid 1px #D0D0D0;background: #ADDFFF;"
|{{#rating:3|10}}
|}&lt;/div&gt;&lt;/div&gt;
&lt;div class="row"  style="margin-bottom:-3px;"&gt;&lt;div class="small-3 columns" &gt;Link to live example&lt;/div&gt;&lt;div class="small-9 columns"&gt;
{| style="border: solid 1px #D0D0D0;"
| See  [[Special:FormEdit/Review/Review:1/Bclemente | Review]] 
|}&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;
&lt;/includeonly&gt;</text>
    <sha1>9c763bc2345b735539f9f07274d6803a88d8585b</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>Template:Download</title>
  <ns>10</ns>
  <id>268</id>
  <revision>
    <id>603</id>
    <parentid>602</parentid>
    <timestamp>2016-02-14T19:10:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="311" xml:space="preserve">&lt;includeonly&gt;
{|
| style="width:100%;background:#eee3d0; font-weight:normal; font-size:80%;border: solid 1px #e0cdab;text-align:left; font-color:#000; padding:5px 5px;margin-bottom:-1px;"|[[Image:Download.png|36px|link=]] Download links and installation instructions may be found here: {{{1}}}
|}
&lt;/includeonly&gt;</text>
    <sha1>3a1fc8aff1d7a1df320b5a9ba2995f21b58b1568</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>Template:Gallery</title>
  <ns>10</ns>
  <id>269</id>
  <revision>
    <id>605</id>
    <parentid>604</parentid>
    <timestamp>2016-02-14T19:10:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision imported</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="220" xml:space="preserve">&lt;includeonly&gt;&lt;div style="display: inline-block;margin: 5px;"&gt;
{|
|{{#widget:LinkedIn Profile
|profile={{{2}}}
|name={{{3}}}
|norelated
}}
|-
|[[File:Gestalt Wiki Framework.png|24px|link=]] {{{1}}}
|}&lt;/div&gt;
&lt;/includeonly&gt;</text>
    <sha1>3f46729562273b5c431aef415b9292cb47da7388</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>File:Download.png</title>
  <ns>6</ns>
  <id>270</id>
  <revision>
    <id>607</id>
    <timestamp>2016-02-14T19:19:56Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>Property:Knowledge type</title>
  <ns>102</ns>
  <id>207</id>
  <revision>
    <id>608</id>
    <parentid>474</parentid>
    <timestamp>2016-02-14T19:28:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="48" xml:space="preserve">This is a property of type [[Has type::String]].</text>
    <sha1>28995a61238b5697df1bb46875d44755b356227c</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>Types of Knowledge</title>
  <ns>0</ns>
  <id>204</id>
  <revision>
    <id>609</id>
    <parentid>475</parentid>
    <timestamp>2016-02-14T19:33:42Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1557" xml:space="preserve">'''TACIT KNOWLEDGE''' 
&lt;br /&gt;
Tacit knowledge resides in an individual’s mind. It is the domain of individuals, not technology. All
individuals have a unique, personal store of knowledge gained from life experiences, training, and formal
and informal networks of friends and professional acquaintances. It includes learned nuances, subtleties,
and work-arounds. Intuition, mental agility, effective responses to crises, and the ability to adapt are also
forms of tacit knowledge. Leaders use tacit knowledge to solve complex problems and make decisions.
They also routinely engage subordinates’ tacit knowledge to improve organizational learning and enhance
unit innovation and performance.
{{New Paragraph}}
'''EXPLICIT KNOWLEDGE''' 
&lt;br /&gt;
Explicit knowledge consists of written or otherwise documented information that can be organized,
applied and transferred using digital (such as computer files) or non-digital (such as paper) means. Explicit
knowledge lends itself to rules, limits, and precise meanings. Examples of explicit knowledge include
dictionaries, official department publications (field manuals, technical manuals, tactics, techniques, and
procedures manuals, Department of the Army pamphlets) and memorandums. Explicit knowledge is
primarily used to support situational awareness and shared understanding as it applies to decisionmaking. 

[[Categorizing Knowledge]]

Source [[Source::Knowledge Management Operations]]

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}
[[Category:KMO Pages]]__NOEDITSECTION__ __NOTOC__</text>
    <sha1>00cfc2eb764438d6c16322a694aa1e2cd83b3a6a</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>Categorizing Knowledge</title>
  <ns>0</ns>
  <id>271</id>
  <revision>
    <id>610</id>
    <timestamp>2016-02-14T19:35:20Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "= Qualitative Knowledge =  = Quantitative Knowledge =  = Reference Knowledge =  = Community Knowledge =  &lt;headertabs /&gt; Source [[Source::Knowledge Management Operations]]  {{#..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="235" xml:space="preserve">= Qualitative Knowledge =

= Quantitative Knowledge =

= Reference Knowledge =

= Community Knowledge =

&lt;headertabs /&gt;
Source [[Source::Knowledge Management Operations]]

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}</text>
    <sha1>5bcf15d1da44741baa19df7ccc2c25bee71d93c5</sha1>
  </revision>
  <revision>
    <id>611</id>
    <parentid>610</parentid>
    <timestamp>2016-02-14T19:37:12Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="259" xml:space="preserve">= Doctrine Knowledge =

= Qualitative Knowledge =

= Quantitative Knowledge =

= Reference Knowledge =

= Community Knowledge =

&lt;headertabs /&gt;
Source [[Source::Knowledge Management Operations]]

{{#set:Name={{PAGENAME}}}}
{{#set:Title Icon={{PAGENAME}}.png}}</text>
    <sha1>dcb4b78257fb2ead6d2d8602aea02405f7ce8a05</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>Knowledge Center</title>
  <ns>0</ns>
  <id>200</id>
  <revision>
    <id>612</id>
    <parentid>466</parentid>
    <timestamp>2016-02-14T19:38:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="599" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}
{{Knowledge Base}}
{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>7e8d7f6ebac240f0b32f634a9b74b0ef819154d5</sha1>
  </revision>
  <revision>
    <id>615</id>
    <parentid>612</parentid>
    <timestamp>2016-02-14T19:42:01Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="651" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}
= KMO =
{{Knowledge Base}}
&lt;br /&gt;
[[Knowledge Management Operations]]

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>cd2ab34fa6974b9dcf46897586da43d907f30b7c</sha1>
  </revision>
  <revision>
    <id>617</id>
    <parentid>615</parentid>
    <timestamp>2016-02-16T05:25:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="582" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>21e5f0a2737b63ed9e5292408193246bac0742b9</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>Template:Knowledge Base</title>
  <ns>10</ns>
  <id>272</id>
  <revision>
    <id>613</id>
    <timestamp>2016-02-14T19:38:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The knowledge base consists of five types of knowledge.  *'''Doctrine Knowledge''' - chunked knowledge from U.S. Army Field Manuals, Joint Operations, and NATO STANAGS. *'''Re..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="738" xml:space="preserve">The knowledge base consists of five types of knowledge.

*'''Doctrine Knowledge''' - chunked knowledge from U.S. Army Field Manuals, Joint Operations, and NATO STANAGS.
*'''Reference Knowledge''' - chunked reference knowledge encyclopedic sources, social science papers published in peer reviewed journals, authoritative aggregators of reference knowledge 
*'''Quantitative Knowledge''' - chunked quantitative knowledge from social science databases, social science papers analyzing quantitative data,social science risk analysis reports interpreting event databases.
*'''Current Knowledge''' - chunked current knowledge from authoritative news sources.
*'''Community Knowledge''' - questions and answers from our communities of interest.</text>
    <sha1>645da2d3698aeeaa1258c9e9f1be4bf2e645ae83</sha1>
  </revision>
  <revision>
    <id>614</id>
    <parentid>613</parentid>
    <timestamp>2016-02-14T19:40:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="686" xml:space="preserve">The knowledge base consists of five types of knowledge.

*'''Doctrine Knowledge''' - chunked knowledge from Air Force Doctrine Documents, Joint Publications, and NATO STANAGS.
*'''Reference Knowledge''' - chunked reference knowledge encyclopedic sources, authoritative aggregators of reference knowledge 
*'''Quantitative Knowledge''' - chunked quantitative knowledge from social science databases, social science papers analyzing quantitative data,social science risk analysis reports interpreting event databases.
*'''Current Knowledge''' - chunked current knowledge from authoritative news sources.
*'''Community Knowledge''' - questions and answers from our communities of interest.</text>
    <sha1>45b20e7a0d63afde3e6907ca98fb6f5a87ee0126</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>MediaWiki:Vector.css</title>
  <ns>8</ns>
  <id>273</id>
  <revision>
    <id>616</id>
    <timestamp>2016-02-16T04:50:22Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "/* CSS placed here will affect users of the Vector skin */ .float-right {    float: right; } .float-left {    float: left; } .left-column {    width:49%;     float: left; } .r..."</comment>
    <model>css</model>
    <format>text/css</format>
    <text bytes="3037" xml:space="preserve">/* CSS placed here will affect users of the Vector skin */
.float-right {
   float: right;
}
.float-left {
   float: left;
}
.left-column {
   width:49%; 
   float: left;
}
.right-column {
   width:49%; 
   float: right;
}
.width-seventy-percent {
   width:69%;
}
.width-thirty-three-percent {
   width:33%;
}
.width-thirty-two-percent {
   width:32%;
}
.margin-left-ten-pixels {
   margin-left: 9px;
}
.width-thirty-percent {
   width:30%;
}
.width-forty-eight-percent {
   width:48%;
}
.three-column {
   width:33%;
   float:left;
}
#main-page #toc {
   display: none;
}
#toc {
   float: right;
}
#main-page p {
   padding: 0px 15px;
}
#main-page li {
   margin-left: 12px;
}
#main-page .small-box {
   border: 1px solid #9fb3c0;
   Xheight: 95px;
   margin-bottom: 20px;
}
#main-page .medium-box {
   border: 1px solid #9fb3c0;
   Xheight: 162px;
   margin-bottom: 20px;
}
#main-page h3 {
   border-bottom: 1px solid #80a8c6;
   padding: 5px 15px;
   background-color: #e2f1fc;
   color: #0e2349;
}
#main-page h2 {
   border-bottom: 1px solid #80a8c6;
   padding: 7px 15px;
   background-color: #cbe5f9;
   color: #0e2349;
   
}
.lss-widget-header {
   width: 100%; 
   background-color: #4159bb; 
   border: 1px solid #4159bb; 
   color: #fff; 
   margin-top: 15px; 
   height: 22px; 
   line-height: 22px;
}

.lss-widget-header {
   width: 100%; 
   background-color: #bddfff;
   Xbackground-color: #dddddd; 
   border: 1px solid #b8b8b8; 
   color: #333; 
   margin-top: 15px; 
   height: 22px; 
   line-height: 22px;
   font-weight: bold;
}

.lss-widget-header-text {
   padding-left: 7px;
   font-family : verdana, geneva, Arial, Helvetica, sans-serif;
   Xfont-size: 90%;
}


.lss-widget-body{
   width: 100%;
   border: 1px solid #b8b8b8;
   border-top: 0px solid #b8b8b8;
   background-color: #f9f9f9;
}

.lss-widget-body-text{
   padding: 4px 7px 5px 7px;
   margin: 0px;
   font-family : verdana, geneva, Arial, Helvetica, sans-serif;
   Xfont-size:90%;
}
.lss-li {
   border-bottom: 1px solid #b8b8b8;
   line-height: 28px;
   height: 28px;
}
.lss-li-no-border {
   line-height: 28px;
   height: 28px;
}
.lss-li-link{
   padding-left: 7px;
}
.lss-widget-footer{
   padding: 0px 5px 0px 5px;
   margin: 0px;
}
.header-lss {
     Xfont-family: "Palatino Linotype","Book Antiqua",Palatino,serif;
     border-bottom: 1px solid #aaa; 
     margin-top: 15px;
     font-size: 16px;
     padding-bottom: 2px;
}
.bold {
     font-weight: bold;
}
#bodyContent table {
   border-collapse: collapse;
   margin: 1em 0;
}
#bodyContent th, #bodyContent td {
   border: 1px solid #999;
   padding: 4px 8px;
}
#bodyContent th, #bodyContent td {
   border: 1px solid #999;
   padding: 4px 8px;
}
#bodyContent td.cell-green {
   background-color:#E0F5D6;
}
#bodyContent th[scope="row"] {
   text-align: left;
   vertical-align: middle;
}
#bodyContent table.complex {

}
#bodyContent table.complex td {
   text-align:center;
}
#bodyContent table.complex tr.tbody {
   border-top: 3px double #999;
}
#pt-login a:before {
   content: "Wiki ";
}</text>
    <sha1>d2882022e71fe13edbf4d5733c967e8d6e04c923</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>MediaWiki:Common.jss</title>
  <ns>8</ns>
  <id>274</id>
  <revision>
    <id>618</id>
    <timestamp>2016-02-16T05:45:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "/* Any JavaScript here will be loaded for all users on every page load. */ /* Any JavaScript here will be loaded for all users on every page load. */ var ttbutton = {..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4845" xml:space="preserve">/* Any JavaScript here will be loaded for all users on every page load. */
/* Any JavaScript here will be loaded for all users on every page load. */
var ttbutton = {
        "imageFile": "images/5/5f/Btn_toolbar_tt.png", // image to be shown on the button (may be a full URL too), 22x22 pixels
        "speedTip": "monotyped text", // text shown in a tooltip when hovering the mouse over the button
        "tagOpen": "&lt;tt&gt;", // the text to use to mark the beginning of the block
        "tagClose": "&lt;/tt&gt;",      // the text to use to mark the end of the block (if any)
        "sampleText": "monotyped text"  // the sample text to place inside the block
};
mwCustomEditButtons.push(ttbutton);
 
var codebutton = {
        "imageFile": "images/2/23/Button_code.png", // image to be shown on the button (may be a full URL too), 22x22 pixels
        "speedTip": "code", // text shown in a tooltip when hovering the mouse over the button
        "tagOpen": "&lt;code&gt;", // the text to use to mark the beginning of the block
        "tagClose": "&lt;/code&gt;",      // the text to use to mark the end of the block (if any)
        "sampleText": "code is here"  // the sample text to place inside the block
};
mwCustomEditButtons.push(codebutton);
 
/**
 * Hide prefix in category
 *
 * @source: www.mediawiki.org/wiki/Snippets/Hide_prefix_in_category
 * @rev: 3
 * @author Krinkle
 */
mw.loader.using( 'jquery.mwExtension', function () {
  var $tplHideCategoryPrefix = $( '#mw-cat-hideprefix' );
  if ( $tplHideCategoryPrefix.length ) {
          var prefix = $tplHideCategoryPrefix.text();
          if ( $.trim( prefix ) === '' ) {
                  prefix = mw.config.get( 'wgTitle' ) + '/';
          }
 
          // Override links
	$( '#mw-pages, #examples' ).find( 'a' ).text( function( i, val ){
             return val.replace( new RegExp( '^' + $.escapeRE( prefix ) ), '' );
        } );
 
        // Hide category column header initial
        $( '#mw-pages' ).find( 'h3' ).hide();
  }
} );
 
/**
 * Hide firstheading
 * @author mwjames
 */
mw.loader.using( 'jquery.mwExtension', function () {
  var hidefirstheading = $( '#smw-hide-firstheading' );
  if ( hidefirstheading.length ) {
        // Hide firstHeading
        $( '#content' ).find( '#firstHeading' ).hide();
  }
} );
 
/**
 * Tab/Panel right slide
 * @author mwjames
 */
 
$("#panel-tab").click( function (event) {
	event.stopPropagation();
	showIfNotVisible( "#panel-content" );
} );
 
function showIfNotVisible( element ) {
	var width = $( '#panel' ).find( 'table').width() + 8; 
	if ( $(element).css( "width" ) == width + 'px' )
		$(element).animate( { width: 4 }, 1500);
	else
		$(element).animate( { width: width }, 1500);
};
 
$( function() {
	var element = $("#panel-content"),
	status = element.attr( 'class' ),
	width = element.find( 'table').width() + 8;
 
	if ( status === 'close' ){
		element
		.width( width )
		.animate( { width: 4 }, 1200);
	} else {
		element
		.width( width );
	}
} );
 
/**
 * Modified bootstrap class for tables
 */
importStylesheet('MediaWiki:Bootstrap.css');
 
/**
 * Additional linked icon for the searchlabel of result format "feed"
 *
 * @since 1.9.0
 *
 * @rev 1
 * @author mwjames
 */
$( '.smw-feed-furtherresults &gt; a' ).addClass( 'feedlink' );
 
/**
 * Prepend w3c validation url
 *
 * @since 1.9.0
 *
 * @rev 1
 * @author mwjames
 */
$( '.feed-validation' ).find( 'a' )
	.attr( 'href','http://validator.w3.org/check?uri=http://www.semantic-mediawiki.org' +
	$( '.feed-validation' ).find( 'a' ).attr( 'href' ) )
	.removeClass( 'feedlink' );
 
/* SMWAgenda */
$(function(){
 
	$('.ag-item-read').click(function(e){
 
		var text = $(this).parent().parent().find('.ag-item-span-text');
		if($(text).height() &gt; 30) {
			$(this).find('a').text('read more');
			$(text).animate({'height':'30px'},250);
		}else{
                        //if($(text).height() == 30 &amp;&amp; $(this).find('a').text() == 'less' ) {
                        //    $(this).find('a').text('read more');
                        //    return false;
                        //}
			$(text).css({'height':'auto'});
			$(this).find('a').text('less')
		}
 
		e.preventDefault();
		return false;
 
	});
 
       $('.ag-item-read').each(function(i,v){
       var text = $(this).parent().parent().find('.ag-item-span-text');
       $(text).css({'height':'auto'});
       $(v).hide();
       });
 
        $('.smw-promo-btn').wrap('&lt;a href="https://semantic-mediawiki.org/wiki/SMWCon_Fall_2013/Tutorial_day" /&gt;');
        $('.smw-promo-btn2').wrap('&lt;a href="https://semantic-mediawiki.org/wiki/SMWCon_Fall_2013/Conference_days" /&gt;');
        $('.smw-promo-btn2015f0').wrap('&lt;a href="https://semantic-mediawiki.org/wiki/SMWCon_Fall_2015/Tutorial_Day" /&gt;');
        $('.smw-promo-btn2015f1').wrap('&lt;a href="https://semantic-mediawiki.org/wiki/SMWCon_Fall_2015/Conference_Days" /&gt;');
 
});</text>
    <sha1>6394e2d711d71343c9bd90f02b4347ecb1164b40</sha1>
  </revision>
  <revision>
    <id>619</id>
    <parentid>618</parentid>
    <timestamp>2016-02-16T05:47:32Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4770" xml:space="preserve">/* Any JavaScript here will be loaded for all users on every page load. */
var ttbutton = {
        "imageFile": "images/5/5f/Btn_toolbar_tt.png", // image to be shown on the button (may be a full URL too), 22x22 pixels
        "speedTip": "monotyped text", // text shown in a tooltip when hovering the mouse over the button
        "tagOpen": "&lt;tt&gt;", // the text to use to mark the beginning of the block
        "tagClose": "&lt;/tt&gt;",      // the text to use to mark the end of the block (if any)
        "sampleText": "monotyped text"  // the sample text to place inside the block
};
mwCustomEditButtons.push(ttbutton);
 
var codebutton = {
        "imageFile": "images/2/23/Button_code.png", // image to be shown on the button (may be a full URL too), 22x22 pixels
        "speedTip": "code", // text shown in a tooltip when hovering the mouse over the button
        "tagOpen": "&lt;code&gt;", // the text to use to mark the beginning of the block
        "tagClose": "&lt;/code&gt;",      // the text to use to mark the end of the block (if any)
        "sampleText": "code is here"  // the sample text to place inside the block
};
mwCustomEditButtons.push(codebutton);
 
/**
 * Hide prefix in category
 *
 * @source: www.mediawiki.org/wiki/Snippets/Hide_prefix_in_category
 * @rev: 3
 * @author Krinkle
 */
mw.loader.using( 'jquery.mwExtension', function () {
  var $tplHideCategoryPrefix = $( '#mw-cat-hideprefix' );
  if ( $tplHideCategoryPrefix.length ) {
          var prefix = $tplHideCategoryPrefix.text();
          if ( $.trim( prefix ) === '' ) {
                  prefix = mw.config.get( 'wgTitle' ) + '/';
          }
 
          // Override links
	$( '#mw-pages, #examples' ).find( 'a' ).text( function( i, val ){
             return val.replace( new RegExp( '^' + $.escapeRE( prefix ) ), '' );
        } );
 
        // Hide category column header initial
        $( '#mw-pages' ).find( 'h3' ).hide();
  }
} );
 
/**
 * Hide firstheading
 * @author mwjames
 */
mw.loader.using( 'jquery.mwExtension', function () {
  var hidefirstheading = $( '#smw-hide-firstheading' );
  if ( hidefirstheading.length ) {
        // Hide firstHeading
        $( '#content' ).find( '#firstHeading' ).hide();
  }
} );
 
/**
 * Tab/Panel right slide
 * @author mwjames
 */
 
$("#panel-tab").click( function (event) {
	event.stopPropagation();
	showIfNotVisible( "#panel-content" );
} );
 
function showIfNotVisible( element ) {
	var width = $( '#panel' ).find( 'table').width() + 8; 
	if ( $(element).css( "width" ) == width + 'px' )
		$(element).animate( { width: 4 }, 1500);
	else
		$(element).animate( { width: width }, 1500);
};
 
$( function() {
	var element = $("#panel-content"),
	status = element.attr( 'class' ),
	width = element.find( 'table').width() + 8;
 
	if ( status === 'close' ){
		element
		.width( width )
		.animate( { width: 4 }, 1200);
	} else {
		element
		.width( width );
	}
} );
 
/**
 * Modified bootstrap class for tables
 */
importStylesheet('MediaWiki:Bootstrap.css');
 
/**
 * Additional linked icon for the searchlabel of result format "feed"
 *
 * @since 1.9.0
 *
 * @rev 1
 * @author mwjames
 */
$( '.smw-feed-furtherresults &gt; a' ).addClass( 'feedlink' );
 
/**
 * Prepend w3c validation url
 *
 * @since 1.9.0
 *
 * @rev 1
 * @author mwjames
 */
$( '.feed-validation' ).find( 'a' )
	.attr( 'href','http://validator.w3.org/check?uri=http://www.semantic-mediawiki.org' +
	$( '.feed-validation' ).find( 'a' ).attr( 'href' ) )
	.removeClass( 'feedlink' );
 
/* SMWAgenda */
$(function(){
 
	$('.ag-item-read').click(function(e){
 
		var text = $(this).parent().parent().find('.ag-item-span-text');
		if($(text).height() &gt; 30) {
			$(this).find('a').text('read more');
			$(text).animate({'height':'30px'},250);
		}else{
                        //if($(text).height() == 30 &amp;&amp; $(this).find('a').text() == 'less' ) {
                        //    $(this).find('a').text('read more');
                        //    return false;
                        //}
			$(text).css({'height':'auto'});
			$(this).find('a').text('less')
		}
 
		e.preventDefault();
		return false;
 
	});
 
       $('.ag-item-read').each(function(i,v){
       var text = $(this).parent().parent().find('.ag-item-span-text');
       $(text).css({'height':'auto'});
       $(v).hide();
       });
 
        $('.smw-promo-btn').wrap('&lt;a href="https://semantic-mediawiki.org/wiki/SMWCon_Fall_2013/Tutorial_day" /&gt;');
        $('.smw-promo-btn2').wrap('&lt;a href="https://semantic-mediawiki.org/wiki/SMWCon_Fall_2013/Conference_days" /&gt;');
        $('.smw-promo-btn2015f0').wrap('&lt;a href="https://semantic-mediawiki.org/wiki/SMWCon_Fall_2015/Tutorial_Day" /&gt;');
        $('.smw-promo-btn2015f1').wrap('&lt;a href="https://semantic-mediawiki.org/wiki/SMWCon_Fall_2015/Conference_Days" /&gt;');
 
});</text>
    <sha1>c63bfcb5c208ebec6ebf2f0ff5792d8c785288b4</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>File:WigleWifi 20160310101110.kml</title>
  <ns>6</ns>
  <id>275</id>
  <revision>
    <id>620</id>
    <timestamp>2016-03-10T18:15:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>EXPLICIT KNOWLEDGE</title>
  <ns>0</ns>
  <id>206</id>
  <revision>
    <id>621</id>
    <parentid>473</parentid>
    <timestamp>2016-03-10T21:08:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="695" xml:space="preserve">{{Glossary-Term
|Glossary Term=EXPLICIT KNOWLEDGE :
|-
|Glossary Definition=Explicit knowledge consists of written or otherwise documented information that can be organized, applied and transferred using digital (such as computer files) or non-digital (such as paper) means. Explicit knowledge lends itself to rules, limits, and precise meanings. Examples of explicit knowledge include dictionaries, official department publications (field manuals, technical manuals, tactics, techniques, and procedures manuals, Department of the Army pamphlets) and memorandums. Explicit knowledge is primarily used to support situational awareness and shared understanding as it applies to decision making.
}}</text>
    <sha1>1291d686f6336ba988a70cd9522c58e5c11c4093</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>Property:Has area</title>
  <ns>102</ns>
  <id>161</id>
  <revision>
    <id>622</id>
    <parentid>370</parentid>
    <timestamp>2016-03-10T21:32:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[Property:Has areq]] to [[Property:Has area]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="351" xml:space="preserve">[[Has type::Quantity]] [[Has description::Used for property values that describe quantities, in particular physical quantities such as time or distance.]] [[Category:Lorem ipsum]]

* [[Corresponds to::1 km²]]
* [[Corresponds to::0.38610 sq mi]]   
* [[Corresponds to::1000 m²]]
* [[Corresponds to::247.1054 acre]]
* [[Corresponds to::988.4215 rood]]</text>
    <sha1>3149176f834dceac9afcd882010a6216a2cbcd69</sha1>
  </revision>
  <revision>
    <id>623</id>
    <parentid>622</parentid>
    <timestamp>2016-03-10T21:40:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="326" xml:space="preserve">[[Has type::Quantity]] [[Has description::Used for property values that describe quantities, in particular physical quantities such as time or distance.]]

* [[Corresponds to::1 km²]]
* [[Corresponds to::0.38610 sq mi]]   
* [[Corresponds to::1000 m²]]
* [[Corresponds to::247.1054 acre]]
* [[Corresponds to::988.4215 rood]]</text>
    <sha1>9a00864fead8a9a52df499d368fa46bd3fa43b76</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>3AN</title>
  <ns>0</ns>
  <id>276</id>
  <revision>
    <id>624</id>
    <timestamp>2016-05-07T02:27:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:Main.png|thumbnail]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="27" xml:space="preserve">[[File:Main.png|thumbnail]]</text>
    <sha1>64afe763c2a7d9ded7516bdefe6804d99b29972b</sha1>
  </revision>
  <revision>
    <id>626</id>
    <parentid>624</parentid>
    <timestamp>2016-05-07T02:32:17Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]</text>
    <sha1>e54eb34d1eea450b1cf6f07b5a9cb68f3b52c20d</sha1>
  </revision>
  <revision>
    <id>627</id>
    <parentid>626</parentid>
    <timestamp>2016-05-07T02:35:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="91" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  
[[File:Statitics.png|frameless|center|Statitics]]</text>
    <sha1>3c3bb8dde059f5de847bea45b80adcafccacabca</sha1>
  </revision>
  <revision>
    <id>629</id>
    <parentid>627</parentid>
    <timestamp>2016-05-07T02:42:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  
[[File:Statitics.png|frameless|center|Statitics]]
[[File:Stats.png|framed|left]]</text>
    <sha1>1bd6c616e0f5f6ab0446c0038c6140f8872c9185</sha1>
  </revision>
  <revision>
    <id>631</id>
    <parentid>629</parentid>
    <timestamp>2016-05-07T02:44:12Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="111" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  
[[File:Statitics.png|frameless|left|]]
[[File:Stats.png|framed|left]]</text>
    <sha1>814be6cba838a39881435370e6472e0c418b2674</sha1>
  </revision>
  <revision>
    <id>632</id>
    <parentid>631</parentid>
    <timestamp>2016-05-07T02:45:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="110" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  
[[File:Statitics.png|frameless|left]]
[[File:Stats.png|framed|left]]</text>
    <sha1>54a15fe4243301e6e23dab7d2b3a70b75d8b891b</sha1>
  </revision>
  <revision>
    <id>633</id>
    <parentid>632</parentid>
    <timestamp>2016-05-07T02:45:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="102" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  
[[File:Statitics.png|link= ]]
[[File:Stats.png|framed|left]]</text>
    <sha1>a3b8818b35aea7dbe5f0bdcb8107080823b0851f</sha1>
  </revision>
  <revision>
    <id>634</id>
    <parentid>633</parentid>
    <timestamp>2016-05-07T02:48:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="73" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  
[[File:Stats1.png|framed|left]]</text>
    <sha1>b1947838d8d1650ba0a1dcd44a2c210561cca2aa</sha1>
  </revision>
  <revision>
    <id>636</id>
    <parentid>634</parentid>
    <timestamp>2016-05-07T02:49:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="66" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  
[[File:Stats1.png|none]]</text>
    <sha1>9cf1b6d54564c026b125e78504b126a9a7a2f9cf</sha1>
  </revision>
  <revision>
    <id>637</id>
    <parentid>636</parentid>
    <timestamp>2016-05-07T03:06:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="70" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  
[[File:Stats.png|none|link]]</text>
    <sha1>fe1d2ccd53e418a8e6a5c27fb22093dd5b6ceb65</sha1>
  </revision>
  <revision>
    <id>638</id>
    <parentid>637</parentid>
    <timestamp>2016-05-07T03:07:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="71" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  
[[File:Stats1.png|none|link]]</text>
    <sha1>d9507585e0f1088bf234c5ab7f8dc0b5a8bc266c</sha1>
  </revision>
  <revision>
    <id>639</id>
    <parentid>638</parentid>
    <timestamp>2016-05-07T03:10:04Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="69" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  
[[File:Stat.png|none|link]]</text>
    <sha1>3dc7930f913ee93c98f4c805ec8c152c8e9972ba</sha1>
  </revision>
  <revision>
    <id>641</id>
    <parentid>639</parentid>
    <timestamp>2016-05-07T03:25:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="534" xml:space="preserve">{{#display_map: 
|rectangles=36.173785232260784,-115.13840317726135:36.17173263294969,-115.14020562171936~ZAPPOS~targeting
|imageoverlays=36.17353407320669,-115.13849973678589:36.172858537963286,-115.13887524604797:; 36.172174336075585,-115.13911128044128:36.17184522417899,-115.13984084129333:; 36.17377657161716,-115.13981938362122:36.173499430515335,-115.14015197753906:; 36.17345612712971,-115.13887524604797:36.17219165771609,-115.13999104499817:~ ~Target
}}

[[File:Main.png|thumbnail|left|link= ]]  
[[File:Stat.png|none|link]]</text>
    <sha1>33d6e8615458a2466c3a036fa4d41d3f9291d98f</sha1>
  </revision>
  <revision>
    <id>642</id>
    <parentid>641</parentid>
    <timestamp>2016-05-07T03:28:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="126" xml:space="preserve">[[File:Main.png|thumbnail|left|link= ]]  [[File:Statitics.png|thumbnail|center|link= ]]

&lt;br /&gt;
[[File:Stats.png|framed|left]]</text>
    <sha1>b4d26a3c617ff4c508de2e7efc46ddc597e3bb9d</sha1>
  </revision>
  <revision>
    <id>643</id>
    <parentid>642</parentid>
    <timestamp>2016-05-07T03:29:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="114" xml:space="preserve">[[File:Statitics.png|thumbnail|link= ]] [[File:Main.png|thumbnail|link= ]] 

&lt;br /&gt;
[[File:Stats.png|framed|left]]</text>
    <sha1>32e14a3813fffabe7276d3e84a32ea96f8ef27a9</sha1>
  </revision>
  <revision>
    <id>644</id>
    <parentid>643</parentid>
    <timestamp>2016-05-07T03:51:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="519" xml:space="preserve">[[File:Statitics.png|thumbnail|link= ]] [[File:Main.png|thumbnail|link= ]] 

&lt;br /&gt;
[[File:Stats.png|framed|left]]

&lt;iframe width="425" height="350" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="http://www.openstreetmap.org/export/embed.html?bbox=-115.14195442199707%2C36.169424883090656%2C-115.13777017593384%2C36.174396211189176&amp;amp;layer=mapnik" style="border: 1px solid black"&gt;&lt;/iframe&gt;&lt;br/&gt;&lt;small&gt;&lt;a href="http://www.openstreetmap.org/#map=17/36.17191/-115.13986"&gt;View Larger Map&lt;/a&gt;&lt;/small&gt;</text>
    <sha1>4b7660c7a967d458cac575e4cd043e27c17dd24d</sha1>
  </revision>
  <revision>
    <id>645</id>
    <parentid>644</parentid>
    <timestamp>2016-05-07T04:18:27Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="145" xml:space="preserve">[[File:Statitics.png|thumbnail|link= ]] [[File:Main.png|thumbnail|link= ]] 

[[File:Openstreets.png|left]]

&lt;br /&gt;
[[File:Stats.png|framed|left]]</text>
    <sha1>952e12f49277f4a13acf21df5bd3cf26b3ca02e5</sha1>
  </revision>
  <revision>
    <id>647</id>
    <parentid>645</parentid>
    <timestamp>2016-05-07T04:20:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="166" xml:space="preserve">[[File:Statitics.png|thumbnail|link= ]] [[File:Main.png|thumbnail|link= ]] 

[[File:Openstreets.png|framed|left|link= ]]

&lt;br /&gt;
[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>216105ec3c67a24a4949e8984b28aa0f710d973e</sha1>
  </revision>
  <revision>
    <id>649</id>
    <parentid>647</parentid>
    <timestamp>2016-05-07T04:23:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="147" xml:space="preserve">
[[File:Openstreets.png|framed|left|link= ]]

&lt;br /&gt;
[[File:Statitics.png|link= ]] [[File:Main.png|link= ]] 

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>a675ea2699127402d640491c6ab232bf97902fb5</sha1>
  </revision>
  <revision>
    <id>650</id>
    <parentid>649</parentid>
    <timestamp>2016-05-07T04:26:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="117" xml:space="preserve">
[[File:Openstreets.png|framed|left|link= ]]

&lt;br /&gt;
[[File:Main.png|link= ]] 

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>2ecb67ac1f5fff60efe613c4db3628552bba5342</sha1>
  </revision>
  <revision>
    <id>652</id>
    <parentid>650</parentid>
    <timestamp>2016-05-07T04:28:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="126" xml:space="preserve">
[[File:Openstreets.png|framed|left|link= ]]

&lt;br /&gt;
[[File:bigview.png|500px|link= ]] 

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>5f260500c9fb2ded1291212604b3a5b3788a9982</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>File:Main.png</title>
  <ns>6</ns>
  <id>277</id>
  <revision>
    <id>625</id>
    <timestamp>2016-05-07T02:28:41Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>File:Statitics.png</title>
  <ns>6</ns>
  <id>278</id>
  <revision>
    <id>628</id>
    <timestamp>2016-05-07T02:35:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>File:Stats.png</title>
  <ns>6</ns>
  <id>279</id>
  <revision>
    <id>630</id>
    <timestamp>2016-05-07T02:43:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>640</id>
    <parentid>630</parentid>
    <timestamp>2016-05-07T03:10:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie uploaded a new version of [[File:Stats.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>File:Stats1.png</title>
  <ns>6</ns>
  <id>280</id>
  <revision>
    <id>635</id>
    <timestamp>2016-05-07T02:48:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>File:Openstreets.png</title>
  <ns>6</ns>
  <id>281</id>
  <revision>
    <id>646</id>
    <timestamp>2016-05-07T04:18:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>648</id>
    <parentid>646</parentid>
    <timestamp>2016-05-07T04:22:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie uploaded a new version of [[File:Openstreets.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160214191014|599">
  <title>File:Bigview.png</title>
  <ns>6</ns>
  <id>282</id>
  <revision>
    <id>651</id>
    <timestamp>2016-05-07T04:27:33Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>3AN</title>
  <ns>0</ns>
  <id>276</id>
  <revision>
    <id>653</id>
    <parentid>652</parentid>
    <timestamp>2016-05-07T04:29:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="139" xml:space="preserve">
[[File:Openstreets.png|500px|framed|left|link= ]]

[[File:bigview.png|500px|framed|link= ]] 
&lt;br /&gt;

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>699396f368dc4d89f0bc75765fb5b85a4981d77b</sha1>
  </revision>
  <revision>
    <id>654</id>
    <parentid>653</parentid>
    <timestamp>2016-05-07T04:30:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="125" xml:space="preserve">
[[File:Openstreets.png|500px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>68634cfef8240e8430a665fbc0d5ccea7c2e1ae4</sha1>
  </revision>
  <revision>
    <id>655</id>
    <parentid>654</parentid>
    <timestamp>2016-05-07T04:30:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="125" xml:space="preserve">
[[File:Openstreets.png|300px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>881628208af4ac421cfda85fd4f9fa2b5d39c63a</sha1>
  </revision>
  <revision>
    <id>656</id>
    <parentid>655</parentid>
    <timestamp>2016-05-07T04:30:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="125" xml:space="preserve">
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>13dce6886378958448a05fb0afa5cf13d0315d35</sha1>
  </revision>
  <revision>
    <id>658</id>
    <parentid>656</parentid>
    <timestamp>2016-05-07T04:38:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="164" xml:space="preserve">[[Ssid-NAME.numbers|SSID NAME NUMBERS]]
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>9926900cceb6f9e844c3678b0dcb4b8731aab7e8</sha1>
  </revision>
  <revision>
    <id>660</id>
    <parentid>658</parentid>
    <timestamp>2016-05-07T06:09:12Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">[[File:WigleWifi 20160507010052.kml]]

[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>c9ea85a07d2ac6d7a0611f00067205f1f093c3fb</sha1>
  </revision>
  <revision>
    <id>663</id>
    <parentid>660</parentid>
    <timestamp>2016-05-07T06:12:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="196" xml:space="preserve">[[File:WigleWifi 20160507010052.kml]] 
[[File:Wifi 20160507010033.csv]]
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>e19372e35a9182fa7d2ffd3807057782146ede57</sha1>
  </revision>
  <revision>
    <id>664</id>
    <parentid>663</parentid>
    <timestamp>2016-05-07T06:14:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="220" xml:space="preserve">[[File:WigleWifi 20160507010052.kml|KML ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv|CSV ]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

[[File:Stats.png|framed|left|link= ]]</text>
    <sha1>e5a9600f2fd25f2a1b3cda6b74acfaf20118203a</sha1>
  </revision>
  <revision>
    <id>665</id>
    <parentid>664</parentid>
    <timestamp>2016-05-07T06:15:47Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="225" xml:space="preserve">[[File:Stats.png|framed|left|link= ]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml|KML ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv|CSV ]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>be102824d415afe39ceb194dad96199a1acea868</sha1>
  </revision>
  <revision>
    <id>666</id>
    <parentid>665</parentid>
    <timestamp>2016-05-07T06:16:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="226" xml:space="preserve">[[File:Stats.png|framed|left|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml|KML ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv|CSV ]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>2e91806c3504f4334f6c0819ca4dd86ab57e2a9e</sha1>
  </revision>
  <revision>
    <id>667</id>
    <parentid>666</parentid>
    <timestamp>2016-05-07T06:16:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="221" xml:space="preserve">[[File:Stats.png|framed|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml|KML ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv|CSV ]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>bc0513518956713fe6bf3c91dc2ac7deb8324228</sha1>
  </revision>
  <revision>
    <id>668</id>
    <parentid>667</parentid>
    <timestamp>2016-05-07T06:17:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="226" xml:space="preserve">[[File:Stats.png|framed|left|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml|KML ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv|CSV ]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>2e91806c3504f4334f6c0819ca4dd86ab57e2a9e</sha1>
  </revision>
  <revision>
    <id>669</id>
    <parentid>668</parentid>
    <timestamp>2016-05-07T06:18:28Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="225" xml:space="preserve">[[IMG:Stats.png|framed|left|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml|KML ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv|CSV ]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>1885c143e3e4abb6066b4f37e04facdb79335e31</sha1>
  </revision>
  <revision>
    <id>670</id>
    <parentid>669</parentid>
    <timestamp>2016-05-07T06:19:31Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="205" xml:space="preserve">[[File:Stats.png|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>8cff5592fbc396e6260786370fb07040f44b3f4f</sha1>
  </revision>
  <revision>
    <id>671</id>
    <parentid>670</parentid>
    <timestamp>2016-05-07T06:20:56Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="212" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>373a64ec833006f4bb38190a223c69a01f13c24a</sha1>
  </revision>
  <revision>
    <id>673</id>
    <parentid>671</parentid>
    <timestamp>2016-05-07T07:14:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="307" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[File:Http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg|thumbnail]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>b86c2cbba2b8597d72b802ba6eb8046db583e0ef</sha1>
  </revision>
  <revision>
    <id>674</id>
    <parentid>673</parentid>
    <timestamp>2016-05-07T07:15:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="292" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[Http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>96d450dc4129b8f2f8553f5a8be64fb158251db6</sha1>
  </revision>
  <revision>
    <id>675</id>
    <parentid>674</parentid>
    <timestamp>2016-05-07T07:18:30Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="297" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[File:http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>841e08da135c54744ee738a48fc3cc5ed124b9f3</sha1>
  </revision>
  <revision>
    <id>676</id>
    <parentid>675</parentid>
    <timestamp>2016-05-07T07:19:01Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="292" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[[http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>720cd858897488d04f2ed8479416f1dadb488788</sha1>
  </revision>
  <revision>
    <id>677</id>
    <parentid>676</parentid>
    <timestamp>2016-05-07T07:19:33Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="290" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;</text>
    <sha1>79dc8ad4c3c48d3cc79c305f2025690b6e84eb86</sha1>
  </revision>
  <revision>
    <id>682</id>
    <parentid>677</parentid>
    <timestamp>2016-05-07T15:06:40Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="348" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;</text>
    <sha1>cee712cf0702682d061a9e66a0dcc664a1f069a9</sha1>
  </revision>
  <revision>
    <id>683</id>
    <parentid>682</parentid>
    <timestamp>2016-05-07T15:08:12Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="406" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>954cac5b9d0c114a0266a91b91e039c2f86316ff</sha1>
  </revision>
  <revision>
    <id>688</id>
    <parentid>683</parentid>
    <timestamp>2016-05-07T15:11:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="406" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

&lt;gallery&gt;
zap0.png
zap1.png
zap6.png
zap7.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap2.png
Zap3.png
&lt;/gallery&gt;</text>
    <sha1>9760ca92e83649a67d8ca59ebee6e6c487df10c8</sha1>
  </revision>
  <revision>
    <id>689</id>
    <parentid>688</parentid>
    <timestamp>2016-05-07T15:12:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="406" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wifi 20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>954cac5b9d0c114a0266a91b91e039c2f86316ff</sha1>
  </revision>
  <revision>
    <id>691</id>
    <parentid>689</parentid>
    <timestamp>2016-05-07T18:34:14Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="409" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:WigleWifi 20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|400px|left|link= ]]

[http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>191dd08e01361b7b26fa5264d7f2fe980db5d8a3</sha1>
  </revision>
  <revision>
    <id>693</id>
    <parentid>691</parentid>
    <timestamp>2016-05-07T18:36:20Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="402" xml:space="preserve">[[File:Stats.png|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px|left|link= ]]

[http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>0ab8c07ddacc10db724a6f1e5dc6eead8059c39a</sha1>
  </revision>
  <revision>
    <id>694</id>
    <parentid>693</parentid>
    <timestamp>2016-05-07T18:37:04Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="408" xml:space="preserve">[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px|left|link= ]]

[http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]

[[File:bigview.png|500px|link= ]] 
&lt;br /&gt;

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>fe531ff064ba549ed5e12c2c0acef20508c3454f</sha1>
  </revision>
  <revision>
    <id>695</id>
    <parentid>694</parentid>
    <timestamp>2016-05-07T18:37:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="408" xml:space="preserve">[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px|left|link= ]]

[http://www.reachback.io/wiki/images/thumb/4/41/Screen.jpg/437px-Screen.jpg]

[[File:bigview.png|300px|link= ]] 
&lt;br /&gt;

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>67129857349d112e8369fb612ec640f9a759a465</sha1>
  </revision>
  <revision>
    <id>696</id>
    <parentid>695</parentid>
    <timestamp>2016-05-07T18:38:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="336" xml:space="preserve">[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px|left|link= ]]
&lt;br /&gt;
[[File:bigview.png|300px|link= ]] 
&lt;br /&gt;

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>d14df916fcc43057ec90c739ee41291db0346361</sha1>
  </revision>
  <revision>
    <id>697</id>
    <parentid>696</parentid>
    <timestamp>2016-05-07T18:39:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="340" xml:space="preserve">[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px|left|link= ]]
&lt;br /&gt;
[[File:bigview.png|300px|link= ]] 
&lt;br /&gt;
---

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>3bf19784ef9c1242487e71ba2ce369d6d911792b</sha1>
  </revision>
  <revision>
    <id>698</id>
    <parentid>697</parentid>
    <timestamp>2016-05-07T18:40:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="354" xml:space="preserve">[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px|left|link= ]]
&lt;br /&gt;
[[File:bigview.png|300px|link= ]] 
&lt;br /&gt;
== Screenshots ==

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>fecacf2841297adc3248aa79d900deef375f8e12</sha1>
  </revision>
  <revision>
    <id>699</id>
    <parentid>698</parentid>
    <timestamp>2016-05-07T18:41:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="359" xml:space="preserve">[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px|left|link= ]]
&lt;br /&gt;
[[File:bigview.png|300px|link= ]] 
{{Newpara}}
== Screenshots ==

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>8d3ab77f27956aed94b8af9bb519b89628a8a378</sha1>
  </revision>
  <revision>
    <id>700</id>
    <parentid>699</parentid>
    <timestamp>2016-05-07T18:41:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="364" xml:space="preserve">[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px|left|link= ]]
&lt;br /&gt;
[[File:bigview.png|300px|link= ]] 
{{NEWPARAGRAPH}}
== Screenshots ==

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>99e49fd01a422d12523d804ef3962c062aaeb2ce</sha1>
  </revision>
  <revision>
    <id>701</id>
    <parentid>700</parentid>
    <timestamp>2016-05-07T18:43:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="356" xml:space="preserve">[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px|left|link= ]]
&lt;br /&gt;
[[File:bigview.png|300px|link= ]] 
{{Para}}
== Screenshots ==

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>440433ef0784b47e5249835e6d3dd9ffcfb99e52</sha1>
  </revision>
  <revision>
    <id>702</id>
    <parentid>701</parentid>
    <timestamp>2016-05-07T18:44:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="329" xml:space="preserve">[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:bigview.png|300px|link= ]] 

[[File:Openstreets.png|300px|link= ]]


{{Para}}

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>0cedfbfdcb13ccaa6b4d3414d2981f3d5f069ed0</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Ssid-NAME.numbers</title>
  <ns>6</ns>
  <id>283</id>
  <revision>
    <id>657</id>
    <timestamp>2016-05-07T04:37:32Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Geo20160507010052.kml</title>
  <ns>6</ns>
  <id>284</id>
  <revision>
    <id>659</id>
    <timestamp>2016-05-07T06:07:45Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>692</id>
    <parentid>659</parentid>
    <timestamp>2016-05-07T18:35:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[File:WigleWifi 20160507010052.kml]] to [[File:Geo20160507010052.kml]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Wireless20160507010033.csv</title>
  <ns>6</ns>
  <id>285</id>
  <revision>
    <id>661</id>
    <timestamp>2016-05-07T06:10:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>662</id>
    <parentid>661</parentid>
    <timestamp>2016-05-07T06:10:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[File:WigleWifi 20160507010033.csv]] to [[File:Wifi 20160507010033.csv]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>690</id>
    <parentid>662</parentid>
    <timestamp>2016-05-07T18:33:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[File:Wifi 20160507010033.csv]] to [[File:Wireless20160507010033.csv]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Screen.jpg</title>
  <ns>6</ns>
  <id>286</id>
  <revision>
    <id>672</id>
    <timestamp>2016-05-07T07:12:23Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Zap0.png</title>
  <ns>6</ns>
  <id>287</id>
  <revision>
    <id>678</id>
    <timestamp>2016-05-07T15:01:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Zap1.png</title>
  <ns>6</ns>
  <id>288</id>
  <revision>
    <id>679</id>
    <timestamp>2016-05-07T15:02:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Zap2.png</title>
  <ns>6</ns>
  <id>289</id>
  <revision>
    <id>680</id>
    <timestamp>2016-05-07T15:02:49Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Zap3.png</title>
  <ns>6</ns>
  <id>290</id>
  <revision>
    <id>681</id>
    <timestamp>2016-05-07T15:03:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Zap4.png</title>
  <ns>6</ns>
  <id>291</id>
  <revision>
    <id>684</id>
    <timestamp>2016-05-07T15:08:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Zap5.png</title>
  <ns>6</ns>
  <id>292</id>
  <revision>
    <id>685</id>
    <timestamp>2016-05-07T15:09:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Zap6.png</title>
  <ns>6</ns>
  <id>293</id>
  <revision>
    <id>686</id>
    <timestamp>2016-05-07T15:09:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507042919|653">
  <title>File:Zap7.png</title>
  <ns>6</ns>
  <id>294</id>
  <revision>
    <id>687</id>
    <timestamp>2016-05-07T15:10:11Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>3AN</title>
  <ns>0</ns>
  <id>276</id>
  <revision>
    <id>703</id>
    <parentid>702</parentid>
    <timestamp>2016-05-07T18:46:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="357" xml:space="preserve">__NOTOC__ __NOEDITSECTION__
[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:bigview.png|300px|link= ]] 

[[File:Openstreets.png|300px|link= ]]


{{Para}}

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>206415caab1fb1500891e2a7affe9935f50992a9</sha1>
  </revision>
  <revision>
    <id>704</id>
    <parentid>703</parentid>
    <timestamp>2016-05-07T18:47:19Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="356" xml:space="preserve">__NOTOC__ __NOEDITSECTION__
[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px|link= ]]

[[File:bigview.png|300px|link= ]] 

{{Para}}

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>383f3d2c7e369a07a3d01a622879cea3e77e5f64</sha1>
  </revision>
  <revision>
    <id>705</id>
    <parentid>704</parentid>
    <timestamp>2016-05-07T18:53:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="342" xml:space="preserve">__NOTOC__ __NOEDITSECTION__
[[File:Stats.png|330px|border|link= ]]
&lt;br /&gt;
[[File:Geo20160507010052.kml ]] 
&lt;br /&gt;
[[File:Wireless20160507010033.csv]]
&lt;br /&gt;
[[File:Openstreets.png|300px]]

[[File:bigview.png|300px]] 

{{Para}}

&lt;gallery&gt;
zap0.png
zap1.png
zap2.png
zap3.png
&lt;/gallery&gt;

&lt;gallery&gt;
Zap4.png
Zap5.png
Zap6.png
Zap7.png
&lt;/gallery&gt;</text>
    <sha1>bf09f67b314e60c09dc44e87c45e8e769861f9ae</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>POS</title>
  <ns>0</ns>
  <id>295</id>
  <revision>
    <id>706</id>
    <timestamp>2016-06-15T23:13:49Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:Gen-char-scrapers.png|thumbnail]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="40" xml:space="preserve">[[File:Gen-char-scrapers.png|thumbnail]]</text>
    <sha1>45b963966e9c87d07658a422d0dd135cffe85507</sha1>
  </revision>
  <revision>
    <id>708</id>
    <parentid>706</parentid>
    <timestamp>2016-06-15T23:16:18Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="37" xml:space="preserve">[[File:Gen-char-scrapers.png|link= ]]</text>
    <sha1>4947ed8681b6d18919325bd5328d0c4c7e9f44a6</sha1>
  </revision>
  <revision>
    <id>709</id>
    <parentid>708</parentid>
    <timestamp>2016-06-15T23:17:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">[[File:Gen-char-scrapers.png|link= ]]

&lt;pdf&gt;pos-ram-scraper-malware.pdf&lt;/pdf&gt;</text>
    <sha1>918f72b1fa2991919af8c66dfa047a3ed0cddf3f</sha1>
  </revision>
  <revision>
    <id>711</id>
    <parentid>709</parentid>
    <timestamp>2016-06-15T23:19:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="70" xml:space="preserve">[[File:Gen-char-scrapers.png|link= ]]

[[pos-ram-scraper-malware.pdf]]</text>
    <sha1>9e4e679d01f076039e15e8a70e812f693627c2b2</sha1>
  </revision>
  <revision>
    <id>712</id>
    <parentid>711</parentid>
    <timestamp>2016-06-15T23:20:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="120" xml:space="preserve">[[File:Gen-char-scrapers.png|link= ]]

[[http://www.reachback.io/wiki/index.php?title=File:Pos-ram-scraper-malware.pdf]]</text>
    <sha1>f5cbc24b061cfc462c4d2ffe18edeea8ae6d3539</sha1>
  </revision>
  <revision>
    <id>714</id>
    <parentid>712</parentid>
    <timestamp>2016-06-15T23:23:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="124" xml:space="preserve">[[File:Gen-char-ram-scrapers.png|link= ]]

[[http://www.reachback.io/wiki/index.php?title=File:Pos-ram-scraper-malware.pdf]]</text>
    <sha1>51f3a7e34c8f8cd64cde0d07a69d5ec8d2b6ae59</sha1>
  </revision>
  <revision>
    <id>715</id>
    <parentid>714</parentid>
    <timestamp>2016-06-15T23:24:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="174" xml:space="preserve">[[File:Gen-char-ram-scrapers.png|link= ]]

[[http://www.reachback.io/wiki/index.php?title=File:Pos-ram-scraper-malware.pdf PoS RAM Scraper Malware
Past, Present, and Future]]</text>
    <sha1>d5414dfa07f4b5b377a30462374bf6d399119ed9</sha1>
  </revision>
  <revision>
    <id>716</id>
    <parentid>715</parentid>
    <timestamp>2016-06-15T23:32:28Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="243" xml:space="preserve">Alina Dexter Pony 1.9 source [[http://cimacell.com/resrch/pos.zip]]

[[File:Gen-char-ram-scrapers.png|link= ]]

[[http://www.reachback.io/wiki/index.php?title=File:Pos-ram-scraper-malware.pdf PoS RAM Scraper Malware
Past, Present, and Future]]</text>
    <sha1>a8de0cff8b741cab5557e1d72e9d1c86bfe6895d</sha1>
  </revision>
  <revision>
    <id>717</id>
    <parentid>716</parentid>
    <timestamp>2016-06-15T23:34:46Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="249" xml:space="preserve">Alina Dexter Pony 1.9  [[http://cimacell.com/resrch/pos.zip| Source Code]]

[[File:Gen-char-ram-scrapers.png|link= ]]

[http://www.reachback.io/wiki/index.php?title=File:Pos-ram-scraper-malware.pdf| PoS RAM Scraper Malware
Past, Present, and Future]</text>
    <sha1>d50dc1500837035351233d65eee55271ed93e2ab</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>File:Gen-char-scrapers.png</title>
  <ns>6</ns>
  <id>296</id>
  <revision>
    <id>707</id>
    <timestamp>2016-06-15T23:15:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>File:Pos-ram-scraper-malware.pdf</title>
  <ns>6</ns>
  <id>297</id>
  <revision>
    <id>710</id>
    <timestamp>2016-06-15T23:18:34Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>File:Gen-char-ram-scrapers.png</title>
  <ns>6</ns>
  <id>298</id>
  <revision>
    <id>713</id>
    <timestamp>2016-06-15T23:22:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>File:Reachback-contracts-in-ricc.png</title>
  <ns>6</ns>
  <id>299</id>
  <revision>
    <id>718</id>
    <timestamp>2016-06-15T23:40:58Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>SocialMediaSensors</title>
  <ns>0</ns>
  <id>300</id>
  <revision>
    <id>719</id>
    <timestamp>2016-06-23T10:51:17Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;nowiki&gt; '''Well built library of valuable resources'''  The social media sensors (monitors) provided here a compiled list of the firm or supplier and the end prediction...."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23877" xml:space="preserve">&lt;nowiki&gt;
'''Well built library of valuable resources'''

The social media sensors (monitors) provided here a compiled list of the firm or supplier and the end prediction.


* Social360 	Custom monitoring and reporting systems 	All 	www.social360monitoring.com 	Paid 	USA / UK / All 	www.social360monitoring.com 
* BrandReact, Inc 	Social Media Monitoring, Reporting &amp; Response 	All: Blogs, News Sites, Consumer Sites (Radar, Kieskeurig etc), Review Sites (Yelp, Travelocity), Social Media (Facebook, Twitter, LinkedIn, YouTube, Orkut, Hyves, etc) 	http://BrandReact.net/brand 	Paid 	USA/Netherlands/Brasil 	Dick Raman 
* iSentia Brandtology 	1-Social and Social Express 	All 	http://www.brandtology.com 	Paid 	USA, China, Hong Kong, Taiwan, Japan, Korea, Australia, Singapore, Malaysia, Indonesia, Thailand, Vietnam, India, New Zealand, Mexico, Brazil, France, Russia, Germany, Portugal, UK, Middle East 	Kelly Choo 
* BrandProtect 	Social Media Monitoring, Reporting &amp; Incident Response Experts 	ALL 	BrandProtect 	Paid 	USA / Canada / UK 	Greg Barrow 
* Needium 	Needium 	Twitter 	http://needium.com/ 	Paid 	USA, Canada, France, UK, more 	Sylvain Carle 
* Dishy! AG 	ReputationTool 	All 	http://reputationtool.com 	Paid 	USA, Canada, Europe, Australia 	Ken Burbary 
* Internet911 	Social Media: Understanding &amp; Protecting your Online Reputation for SMBs 	ALL 	Internet911 	Paid 	USA / Canada 	Greg Barrow 
* Actionly 	Actionly 	Twitter, Facebook, Blogs, YouTube, Buzz, Flickr 	http://www.actionly.com 	Paid 	USA 	Actionly 
* Ascent Labs, Inc. 	StatsMix 	All 	http://statsmix.com/ 	Free 	USA 	Sasha Kovaliov 
* Asterisq 	Mentionmap 	Twitter 	http://apps.asterisq.com/mentionmap/# 	Free 	USA 	Bob Hodgson 
* Attensity 	Market Voice 	All 	http://www.attensity.com 	Paid 	USA 	Ken Burbary 
* Backtype 	Connect 	Blogs, Twitter, Friendfeed 	http://www.backtype.com/connect 	Free 	USA 	Ken Burbary 
* Bantam Networks 	Bantam Live 	Twitter 	http://www.bantamlive.com/ 	Paid 	USA 	Bob Hodgson 
* Betaworks 	Chartbear 	Twitter 	http://www.chartbeat.com 	Paid 	USA 	Nathan Folkman 
* BitConfused 	BuzzDing 	All 	http://www.buzzding.com 	Paid 	USA 	Ken Burbary 
* Bivings Group 	Impactwatch 	All 	http://impactwatch.com 	Paid 	USA 	Dave Murr 
* Biz360 Inc. 	Biz360 	All 	Biz360 	Paid 	USA 	Len Kendall 
* Buzzersation 	Buzzersation 	All 	http://www.buzzersation.com 	Paid 	USA 	Ken Burbary 
* Buzzient 	Buzzient Enterprise 	All 	http://www.buzzient.com 	Paid 	USA 	Ken Burbary 
* BuzzLogic 	BuzzLogic Insight 	All 	http://www.buzzlogic.com 	Paid 	USA 	Ken Burbary 
* BuzzStream 	BuzzStream 	All 	http://www.buzzstream.com 	Free 	USA 	Ed Hartigan 
* ChatterBeacon 	ChatterBeacon 	Facebook 	http://chatterbeacon.com 	Free 	USA 	Ken Burbary 
* Cision 	Cision Social Media 	All 	http://us.cision.com/products_services/cision_social_media/overview.asp 	Paid 	USA 	Ken Burbary 
* Collecta 	Collecta 	Micromedia, Blogs, Video 	Collecta.com 	Free 	USA 	Len Kendall 
* Collective Intellect 	CI:View and CI:Insight 	All 	http://www.collectiveintellect.com 	Paid 	USA 	Ken Burbary 
* Converseon 	Conversation Miner 	All 	http://www.converseon.com 	Paid 	USA 	Ken Burbary 
* Conversition 	TweetFeel 	Twitter 	TweetFeel 	Free 	USA 	Len Kendall 
* CoTweet 	CoTweet 	Twitter 	http://www.cotweet.com 	Free 	USA 	Ed Hartigan 
* Crimson Hexagon 	Voxtrot 	All 	http://www.crimsonhexagon.com 	Paid 	USA 	Jay Baer 
* Crowd Favorite 	Addictomatic 	All 	http://addictomatic.com 	Free 	USA 	Michelle Sullivan 
* CustomScoop 	BuzzPerception 	Blogs 	http://www.customscoop.com 	Paid 	USA 	Chip Griffin 
* CustomScoop 	ClipIQ 	All 	http://www.customscoop.com 	Paid 	USA 	Chip Griffin 
* Cymfony 	Maestro 	All 	http://www.cymfony.com 	Paid 	USA 	Ken Burbary 
* Cyveillance 	Cyveillance 	All 	http://www.cyveillance.com 	Paid 	USA 	Ken Burbary 
* Decooda 	Decooda 	All 	http://decooda.com 	Paid 	USA 	Ken Burbary 
* Digimind 	Digimind Meta-Search 	All 	http://www.digimind.com 	Paid 	USA 	Ken Burbary 
* Dow Jones 	Dow Jones Insight 	All 	http://solutions.dowjones.com 	Paid 	USA 	Ken Burbary 
* eCairn 	Conversation 	All 	http://www.ecairn.com 	Paid 	USA 	Ken Burbary 
* Echometrix 	ThePulse 	All 	http://www.echometrix.com 	Paid 	USA 	Adam Smilowitz 
* Effyis 	Boardreader 	Forums 	http://boardreader.com 	Free 	USA 	Ken Burbary 
* Emerge Technology Group 	Socialscape 	All 	http://www.socialscape.biz 	Paid 	USA 	Ken Burbary 
* EvoApp 	EvoApp 	All 	http://www.evoapp.com 	Paid 	USA 	Ken Burbary 
* Facebook 	Search 	Facebook 	http://www.facebook.com/search 	Free 	USA 	Ken Burbary 
* Facebook 	Lexicon 	Facebook 	http://www.facebook.com/lexicon 	Free 	USA 	Ken Burbary 
* Glam Media 	Tinker 	Twitter 	http://www.tinker.com 	Free 	USA 	Ken Burbary 
* Google 	Blogsearch 	Blogs 	http://blogsearch.google.com 	Free 	USA 	Ken Burbary 
* GroupHigh 	GroupHigh 	Blogs 	http://www.grouphigh.com 	Paid 	USA 	Ken Burbary 
* Hubspot 	Twitter Grader 	Twitter 	Twitter Grader 	Free 	USA 	Len Kendall 
* Infegy 	Social Radar 	All 	Social Radar 	Paid 	USA 	Len Kendall 
* Inifinimedia 	StartPR 	All 	http://startpr.com 	Paid 	USA 	Ken Burbary 
* Insttant 	Insttant 	Twitter 	http://insttant.com 	Paid 	USA 	http://www.kenburbary.com 
* Iterasi 	Positive Press 	All 	http://www.iterasi.net 	Paid 	USA 	Ken Burbary 
* JD Power 	Umbria 	All 	http://www.jdpowerwebintelligence.com 	Paid 	USA 	Ken Burbary 
* Jive Software 	Jive Social Media Engagement 	All 	http://www.jivesoftware.com 	Paid 	USA 	Ken Burbary 
* Kaleidico 	Eavesdropper 	All 	http://kaleidico.com 	Paid 	USA 	Ken Burbary 
* Kantar Video 	Videolytics 	Video 	http://www.kantarvideo.com 	Paid 	USA 	Ken Burbary 
* Klout 	Klout 	Twitter 	http://klout.com 	Free 	USA 	Benjamin Schwarz 
* Linkfluence 	Linkfluence 	All 	http://linkfluence.net 	Paid 	USA 	Ken Burbary 
* ListenLogic 	Resonate 	All 	http://www.listenlogic.com 	Paid 	USA 	Ken Burbary 
* Lithium Technologies 	Lithium Social Media Monitoring 	All 	http://www.lithium.com 	Paid 	USA 	Ken Burbary 
* Looxii 	Looxii 	Social Media 	http://www.looxii.com/ 	Paid 	USA 	Alex Griffiths 
* Loudpixel 	Loudpixel 		http://loudpixel.com/ 	Paid 	USA 	Alex Griffiths 
* Martiz Research 	Evolve24 	The Mirror 	http://www.evolve24.com 	Paid 	USA 	Ken Burbary 
* Medimix 	Scanbuzz 	All (niche - pharma) 	http://www.medimix.net/ 	Paid 	USA 	Ed Hartigan 
* Meltwater 	Buzz 	All 	http://www.meltwater.com 	Paid 	USA 	Ken Burbary 
* Meltwater Group 	BuzzGain 	All 	BuzzGain 	Paid 	USA 	Christine Fife 
* Meltwater Group 	Icerocket 	Blogs 	http://www.icerocket.com 	Free 	USA 	Ken Burbary 
* Meltwater Group 	JitterJam 	All 	http://www.jitterjam.com/ 	Paid 	USA 	E. Christopher Clark 
* Milestone Internet Marketing 	eBuzz Connect 	All 	http://www.ebuzzconnect.com/ 	Paid 	USA 	Mike Supple 
* Monitter 	Monitter 	Twitter 	http://www.monitter.com 	Free 	USA 	Ken Burbary 
* Moreover Technologies 	Newsdesk 	All 	http://w.moreover.com 	Paid 	USA 	Ken Burbary 
* MotiveQuest 	MotiveQuest 	All 	http://www.motivequest.com 	Paid 	USA 	Ken Burbary 
* mReplay 	Livedash 	All 	http://www.livedash.com 	Free 	USA 	Ken Burbary 
* NetBase 	ConsumerBase 	All 	http://www.netbase.com 	Paid 	USA 	Ken Burbary 
* Networked Insights 	SocialSense 	All 	http://www.networkedinsights.com 	Paid 	USA 	Ken Burbary 
* New Media Strategies 	AIM 	All 	http://newmediastrategies.net 	Paid 	USA 	Ken Burbary 
* Nielsen 	Blogpulse 	Blogs 	http://www.blogpulse.com 	Free 	USA 	Ken Burbary 
* Nielsen 	My BuzzMetrics 	All 	http://en-us.nielsen.com/tab/product_families/nielsen_buzzmetrics 	Paid 	USA 	Ken Burbary 
* Now Metrix 	Trendrr 	All 	http://www.trendrr.com 	Free 	USA 	Ken Burbary 
* NutShellMail 	NutShellMail 	Social Networks 	http://nutshellmail.com 	Free 	USA 	Ken Burbary 
* OneRiot 	OneRiot 	Twitter, Digg, YouTube 	http://www.oneriot.com 	Free 	USA 	Ed Hartigan 
* Overdrive Interactive 	Social Media Dashboard 	All 	http://www.ovrdrv.com 	Paid 	USA 	Jeff Selig 
* Overtone 	Open Mic 	All 	http://www.overtone.com 	Paid 	USA 	Ed Hartigan 
* PeopleBrowsr 	Analytic.ly 	All 	http://analytics.peoplebrowsr.com 	Paid 	USA 	Ken Burbary 
* Pidgin Technologies 	Boardtracker 	Forums 	http://www.boardtracker.com 	Free 	USA 	Ken Burbary 
* Position2 	Brand Monitor 	All 	Position2 Brand Monitor 	Paid 	USA 	Position2 
* PR Newswire 	eWatch 	Blogs 	http://ewatch.prnewswire.com 	Paid 	USA 	Ken Burbary 
* Raven 	Raven 	All 	Raven SEO Tools 	Paid 	USA 	Roy Morejon 
* Reputation Defender 	Reputation Defender 	All 	http://www.reputationdefender.com 	Paid 	USA 	Ken Burbary 
* ReputationHQ 	My Reputation Manager 	All 	http://reputationhq.com 	Paid 	USA 	Ken Burbary 
* Reputationobserver 	Reputationobserver 	All 	http://www.reputationobserver.com 	Paid 	USA 	Sebastian 
* ReviewIQ 	ReviewIQ 	All 	http://www.reviewiq.net 	Paid 	USA 	Ken Burbary 
* Revinate 	Revinate 	All 	http://www.revinate.com 	Paid 	USA 	Ken Burbary 
* RightNow 	RightNow CX 	All 	http://www.rightnow.com/ 	Paid 	USA 	Alex Griffiths 
* Samepoint 	Samepoint 	All 	http://www.samepoint.com 	Free 	USA 	Ken Burbary 
* Sensidea 	SocialSeek 	Blogs, Video, Micromedia, Photos 	SocialSeek 	Free 	USA 	Len Kendall 
* SiteQuest Technologies 	Compliance WatchDog 	All 	http://www.sitequesttech.com 	Paid 	USA 	Ken Burbary 
* Social Mention 	Social Mention 	All 	http://socialmention.com 	Free 	USA 	Ken Burbary 
* SocialOomph 	SocialOomph 	Twitter 	SocialOomph 	Free 	USA 	Jason Mayes 
* Spiral16 	Spark 	All 	http://www.spiral16.com 	Paid 	USA 	Ken Burbary 
* Sports Media Challenge 	Buzz Manager  	All 	http://www.sportsmediachallenge.com/buzzmanager/index.html 	Paid 	USA 	Ryan Stephens 
* Sprinklr 	Sprinklr 	Twitter and Facebook 	http://www.sprinklr.com/ 	Paid 	USA 	Christine Fife 
* Sprout Social 	Sprout Social 	All 	http://sproutsocial.com/ 	Paid 	USA 	Alex Griffiths 
* SWIX 	SWIX 	All 	http://swixhq.com/SWIX.html 	Paid 	USA 	Sasha Kovaliov 
* Tealium 	Tealium SM 	All 	http://www.tealium.com/products/social-media/index.html 	Paid 	USA 	Tony Felice 
* Technorati 	Blogsearch 	Blogs 	http://technorati.com 	Free 	USA 	Ken Burbary 
* Techrigy 	SM2 	All 	http://www.alterian-social-media.com 	Paid 	USA 	Ken Burbary 
* Telligent 	Telligent Analytics 	All 	http://telligent.com/products/telligent_analytics/ 	Paid 	USA 	Peter Brenchley 
* The Search Monitor 	The Search Monitor (Starter and Pro) 	All 	http://www.thesearchmonitor.com/ 	Free 	USA 	Christine Fife 
* TipTop Technologies 	TipTop 	Twitter, Amazon reviews 	http://feeltiptop.com 	Free 	USA 	Ken Burbary 
* Todaypulse 	Todaypulse 	All 	http://todaypulse.com 	Paid 	USA 	Justin Walsh 
* Topsy Labs 	Topsy 	Twitter 	http://topsy.com/ 	Free 	USA 	Christine Fife 
* Trackur LLC. 	Trackur 	All 	Trackur 	Paid 	USA 	Roy Morejon 
* Twazzup 	Twazzup 	Twitter 	http://www.twazzup.com 	Free 	USA 	Ken Burbary 
* TweetBeep 	TweetBeep 	Twitter 	http://www.tweetbeep.com 	Free 	USA 	Michael Jensen 
* Tweetlytics 	Tweetlytics 	Twitter 	http://www.tweetlytics.com/ 	Paid 	USA 	Alex Griffiths 
* TweetReach 	TweetReach 	Twitter 	TweetReach 	Free 	USA 	Jason Mayes 
* Twitter 	Twitter Search 	Twitter 	http://search.twitter.com 	Free 	USA 	Ken Burbary 
* TwitterCounter 	TwitterCounter 	Twitter 	TwitterCounter 	Free 	USA 	Jason Mayes 
* Viralheat 	Viralheat 	All 	http://www.viralheat.com 	Paid 	U.S.A 	Greg 
* Visible Measures 	TruReach, Video Engagement 	Video 	http://www.visiblemeasures.com 	Paid 	USA 	Pierre-Loïc Assayag 
* Visible Technologies 	Visible Intelligence 	All 	http://www.visibletechnologies.com 	Paid 	USA 	Ken Burbary 
* Vocus, Inc. 	Vocus PR 	All 	http://www.vocus.com/content/social-media.asp 	Paid 	USA 	Ken Burbary 
* Web Analytics Demystified 	Twitalyzer 	Twitter 	http://www.twitalyzer.com 	Free 	USA 	Ken Burbary 
* Who's Talkin 	Who's Talkin 	ALL 	Who's Talkin 	Paid 	USA 	Roy Morejon 
* Wildfire 	Monitor 	Twitter, Facebook 	http://monitor.wildfireapp.com 	Free 	USA 	Ken Burbary 
* Wool.Labs 	WebDig, DigTV, AdSlider 	All Internet + TV/Radio 	http://woollabs.com 	Paid 	USA 	Steve Chiles 
* Xerocity Design Group 	twitt(url)y 	Twitter 	http://twitturly.com/ 	Free 	USA 	Claudius Gerstner 
* YackTrack 	YackTrack 	Blogs 	http://yacktrack.com 	Free 	USA 	Rob Diana 
* MutualMind 	MutualMind 	All 	http://mutualmind.com 	Paid 	US 	Babar Bhatti 
* Geofeedia 	Geofeedia 	Twitter, Instagram, Fickr, Picasa, YouTube 	http://www.geofeedia.com 	Paid 	United States 	Ken Burbary 
* Social Agency Inc 	SpredFast 	All 	http://spredfast.com 	Paid 	United States 	Ken Burbary 
* Social Report 	Social Report 	All 	https://www.socialreport.com 	Paid 	United States 	Ken Burbary 
* DigitalMR  	Social Nuggets 	All 	http://www.digital-mr.com 	Paid 	UK, USA, Cyprus 	Michalis A. Michael 
* Integrasco AS 	WoMPortal  	All 	Integrasco 	Paid 	UK, Norway, China 	Integrasco 
* 1000Heads 	WOMTrak 	All 	http://www.1000heads.com 	Paid 	UK 	Ken Burbary 
* Brandwatch 	Brandwatch 	All 	http://www.brandwatch.net 	Paid 	UK 	Fabrice Retkowsky 
* Inuda Innovations 	HowSociable 	All 	http://howsociable.com/ 	Free 	UK 	Christine Fife 
* Macranet 	Sentiment Metrics 	All 	http://www.sentimentmetrics.com 	Paid 	UK 	Ed Hartigan 
* Market Sentinel 	LiveBuzz 	All 	http://www.marketsentinel.com/ 	Paid 	UK 	Christine Fife 
* MediaBadger 	Mediasphere360 	All 	http://www.mediabadger.com 	Paid 	UK 	Ken Burbary 
* Noteca 	Noteca 	All 	http://www.noteca.com 	Paid 	UK 	Ken Burbary 
* Onalytica 	Direct Access - InfluenceMonitor 	All 	http://www.onalytica.com 	Paid 	UK 	Ken Burbary 
* Rees Bradley Hepburn Ltd 	RBH Radar 	All 	http://www.rbh.co.uk 	Paid 	UK 	Ken Burbary 
* Simpleweb Ltd. 	Media Genius 	All 	http://www.mediageniusapp.com 	Paid 	UK 	Ken Burbary 
* Sodash 	Sodash 	Twitter, Facebook, email, specific blogs via RSS 	soda.sh/ 	Paid 	UK 	Alex Griffiths 
* Tick Tock Boom Digital 	BoomSonar 	All 	http://www.boomsonar.com 	Paid 	Turkey 	Ken Burbary 
* FinchLine 	FinchLine 	All 	http://www.finchline.nl 	Paid 	The Netherlands 	Ken Burbary 
* New Music Labs BV 	Tribe Monitor 	Online (MySpace, Hyves, Last.fm, Twitter, Google Analytics, FaceBook, Google Video, Youtube) 	Tribe Monitor 	Free 	The Netherlands 	New Music Labs 
* MeMo News AG 	MeMo News Monitoring 	All: News, Blogs, Forums, Social Media (Facebook, Twitter, Google+, Youtube ...) 	MeMoNews.com 	Paid 	Switzerland 	Stefan Vetter 
* Netbreeze 	CommMonitor 	All 	http://www.netbreeze.ch 	Paid 	Switzerland 	Ken Burbary 
* Intelliwell 	Informant 	All 	http://informant.se 	Paid 	Sweden 	Ken Burbary 
* Patch6 AB 	Silverbakk Briefing Room 	All 	http://www.silverbakk.com 	Paid 	Sweden 	Ken Burbary 
* Retriever  	Retriever 	Blogs, Twitter, Facebook 	http://www.retriever.se 	Paid 	Sweden 	Ken Burbary 
* Cierzo Development S.L 	Smmart 	All 	http://www.smmart.es 	Paid 	Spain 	Ken Burbary 
* Habber tec 	Social Web Intelligence 	All 	http://socialwebintelligence.com 	Paid 	Spain 	Ken Burbary 
* Tinval Sistemes S.L. 	BrandChats 	All 	http://www.brandchats.com 	Paid 	Spain 	
* WhatHashtag by Círculo Rojo 	WhatHashtag 	Twitter 	http://whathashtag.circulorojo.es/ 	Free 	Spain 	Álex Rubio @alexrbn (Círculo Rojo) 
* Daumsoft 	UCCmetrics 	All 	http://www.daumsoft.com 	Paid 	South Korea 	Ken Burbary 
* Brands Eye 	Brands Eye 	All 	http://www.brandseye.com 	Paid 	South Africa 	Ken Burbary 
* ThoughtBuzz 	ThoughtBuzz 	All 	http://www.thoughtbuzz.net 	Paid 	Singapore, Malaysia, Philippines, Indonesia  	
* JamIQ 	JamIQ 	All 	http://www.jamiq.com 	Paid 	Singapore 	
* YouScan 	YouScan 	All 	http://www.youscan.ru 	Paid 	Russia, Ukraine 	Alexey Orap 
* TreeWorks 	Zelist Monitor 	Blogs, Twitter, online media, Facebook, some of the most important discussion boards/forums in Romania 	http://www.zelistmonitor.ro 	Paid 	Romania 	Catalin Tenita 
* BrandReact Nederland BV 	Social Media Monitoring, Reporting &amp; Response 	All: Blogs, News Sites, Consumer Sites (Radar, Kieskeurig etc), Review Sites (Yelp, Travelocity), Social Media (Facebook, Twitter, LinkedIn, YouTube, Orkut, Hyves, etc) 	BrandReact.NL 	Paid 	Netherlands, Belgium, Luxemburg 	Dick Raman 
* Clipit News 	Clipit - online media monitoring 	All (dutch) 	http://www.clipit.nl 	Paid 	Netherlands 	Sjaak Janssen 
* iMonitoring 	iMonitoring 	All 	http://www.internetmonitoring.nl 	Paid 	Netherlands 	Ken Burbary 
* Teezir  	eCare 	All 	http://www.teezir.com 	Paid 	Netherlands 	Ken Burbary 
* TraceBuzz 	TraceBuzz 	All 	http://www.tracebuzz.com 	Paid 	Netherlands 	Ken Burbary 
* Twitter Analyzer 	Twitter Analyzer 	Twitter 	http://twitteranalyzer.com 	Free 	Netherlands 	Claudius Gerstner 
* Trendiction 	Trendiction Search 	All 	http://www.trendiction.com 	Paid 	Luxembourg 	Ken Burbary 
* Expert System 	Cognito Monitor 	All 	http://www.expertsystem.net 	Paid 	Italy, USA 	Ken Burbary 
* BuzzDetector 	BuzzDetector 	All 	http://www.buzzdetector.com 	Paid 	Italy 	Ken Burbary 
* infoFactory 	ifMONITOR 	All 	http://www.infofactory.it 	Paid 	Italy 	Ken Burbary 
* SocialPointer 	Social Pointer 	All 	http://www.socialpointer.com 	Free 	Israel 	Yair Benyami 
* Katapedia 	Katapedia 	All 	http://www.katapedia.com 	Paid 	Indonesia 	Deddy Rahman 
* Beevolve 	Social Media Monitoring &amp; Engagement Platform 	All 	http://www.beevolve.com/ 	Paid 	India 	Christine Fife 
* Factualz 	Factualz 	All 	http://www.factualz.com 	Paid 	India 	Ken Burbary 
* Omllion 	Omllion 	All 	http://www.omllion.com 	Paid 	India 	Ken Burbary 
* Webfluenz  	Webfluenz  	All 	http://webfluenz.com 	Paid 	India 	Ken Burbary 
* Brandmonitor 	Brandmonitor 	All 	http://www.brandmonitor.hu 	Paid 	Hungary 	
* Glerts 	Glerts 	All media indexed by Google 	http://www.glerts.com/beta 	Free 	Global 	http://www.glert.com 
* Cognita AG 	blueReport 	Blogs, Twitter 	http://www.bluereport.net 	Paid 	Germany, Switzerland, Austria  	Ken Burbary 
* Mindlab Solutions GmbH 	netmind Sphere 	All 	http://www.mindlab.de 	Paid 	Germany, Austria, Switzerland 	Heinz D. Schultz 
* Ethority 	Gridmaster 	All 	http://www.ethority.net 	Paid 	Germany 	Ken Burbary 
* Frank Westphal 	Rivva 	Blogs, Twitter 	http://rivva.de/ 	Free 	Germany 	Claudius Gerstner 
* iMooty 	iMooty 	News 	http://www.imooty.eu 	Free 	Germany 	Ken Burbary 
* infospeed 	web2monitor™ 	All 	infospeed 	Paid 	Germany 	Social Media Magazin 
* Landau Media 	Landau Media Monitoring Internet 	All 	http://www.landaumedia.de 	Paid 	Germany 	Ken Burbary 
* net-clipping 	net-clipping 	Online, Social Media, amazon, facebook 	http://net-clipping.de 	Paid 	Germany 	Cornelia Horst 
* New Communication 	Reputation Control 	All 	http://www.reputation-control.de 	Paid 	Germany 	
* TwentyFeet 	TwentyFeet 	Twitter, Facebook, YouTube, Google Analytics, bit.ly, MySpace 	http://www.twentyfeet.com 	Paid 	Germany 	Paul Herwarth 
* User Interface Design GmbH 	What's Up?! 	Twitter 	http://whatsup.uid.com 	Free 	Germany 	Ken Burbary 
* Webbosaurus 	Webboboard 	All 	webbosaurus.de 	Paid 	Germany 	Webbosaurus 
* AT Internet 	BuzzWatcher 	All 	http://en.atinternet.com 	Paid 	France 	Ken Burbary 
* AT Internet 	BuzzWatcher 	All 	http://en.atinternet.com/Products/BuzzWatcher.aspx 	Paid 	France 	Ken Burbary 
* Semiocast 	Semioboard 	All 	Semioboard.com 	Paid 	France 	Jean-Charles Campagne 
* Statsit  	Monitor 	All 	http://www.statsit.com 	Paid 	Finland, Malaysia 	Ken Burbary 
* M-Brain 	M-Brain 	All 	http://www.m-brain.com/ 	Paid 	Finland 	Joakim Nyberg 
* Whitevector 	Whitevector 	All 	http://www.whitevector.com 	Paid 	Finland 	Ken Burbary 
* Blogmeter 	Blogmeter 	All 	http://www.blogmeter.eu 	Paid 	Europe 	Barbara Aversano 
* Replise 	Replise 	All 	Replise.com 	Paid 	Europe 	
* Socialware 	Asomo 	All 	http://www.asomo.net 	Paid 	Europe 	Ken Burbary 
* Synthesio 	Synthesio 	All 	Synthesio 	Paid 	Europe 	Len Kendall 
* BrandMetric 	BrandMetric 	All 	http://www.brandmetric.com 	Paid 	Chile 	Ken Burbary 
* DNA13 	dnaMonitor 	All 	http://www.dna13.com/ 	Paid 	Canada 	Christine Fife 
* Lola 	Variety of off-the-shelf tools and proprietary technologies 	All online sources 	Lola 	Paid 	Canada 	Luis Vieira 
* MediaMiser 	MediaMiser Enterprise 	All 	http://www.mediamiser.com 	Paid 	Canada 	Ken Burbary 
* MyFrontSteps 	Steprep 	All 	http://steprep.myfrontsteps.com 	Free 	Canada 	Ken Burbary 
* PostRank Inc 	PostRank 	RSS Enabled Content, Blogs, Social Networks &amp; Hubs 	PostRank 	Free 	Canada 	PostRank 
* RepuMetrix 	RepuTrace, RepuTrack 	All 	http://www.repumetrix.com 	Paid 	Canada 	Ken Burbary 
* Salesforce 	Radian6 	All 	http://www.radian6.com 	Paid 	Canada 	Ken Burbary 
* Syncapse Corp 	Socialtalk 	Twitter, Facebook, Wordpress, Moveable Type 	http://www.socialtalk.com 	Paid 	Canada 	Alex Griffiths 
* Sysomos 	MAP, Heartbeat 	All 	http://www.sysomos.com 	Paid 	Canada 	Ken Burbary 
* White Noise Inc. 	White Noise 	All 	http://www.herdthenoise.com 	Paid 	Canada 	Ken Burbary 
* Chleba Agencia digital 	Social media Monitor 	Google Blogs / Flickr / Twitter / Google News / Yahoo Respostas / Facebook / Orkut Comunidades / Reclame Aqui / YouTube  	http://www.socialmediamonitor.com.br/ 	Paid 	Brazil 	Henrique Rangel 
* Scup 	Scup 	All 	http://www.scup.com.br 	Paid 	Brazil 	Ken Burbary 
* Attentio 	Buzz Report 	All 	http://www.attentio.com 	Paid 	Belgium 	Simon McDermott 
* BrandFractal  	CommandCenter, Sodalyzer, social data analytics 	All 	http://www.brandfractal.com 	Paid 	Belgium 	Ken Burbary 
* Engagor 	Engagor Insights 	All 	http://www.engagor.com 	Paid 	Belgium 	Ken Burbary 
* BuzzNumbers 	BuzzNumbers 	All 	http://www.buzznumbershq.com 	Paid 	Australia 	Ken Burbary 
* e-CBD 	Dialogix 	All 	http://www.dpdialogue.com.au 	Paid 	Australia 	Ken Burbary 
* StreamWall 	StreamWall 	All 	http://www.socialmediamonitoring.com.au 	Paid 	Australia 	Ken Burbary 
* Walkley 	Walkley 	All 	http://www.walkley.com.au/ 	Paid 	Australia 	Walkley 
* Flaptor 	Trendistic (formerly Twist) 	Twitter 	http://trendistic.com 	Free 	Argentina 	Claudius Gerstner 
* SocialMetrix 	SocialMetrix 	All 	http://www.SocialMetrix.com 	Paid 	Argentina 	Sebastian Rosenfeld 
* Buzzcapture B.V. 	Buzzcapture 	All 	http://www.buzzcapture.com 	Paid 	Amsterdam 	Ken Burbary 
* Eurospider Information Technology AG 	Media Monitoring &amp; Management 	All 	Media Monitoring &amp;amp; Management 	Paid 	All 	Loig Roumois 
* uberVU 	uberVU 	blogs, Twitter, Digg, FriendFeed and many more 	http://www.ubervu.com/ 	Free 		Bryan Skelton 
* WhoUnfollowedMe 	WhoUnfollowedMe 	Twitter 	WhoUnfollowedMe 	Free 		Jason Mayes </text>
    <sha1>286116290a2feab2ce5e6a9f54691e6406742feb</sha1>
  </revision>
  <revision>
    <id>726</id>
    <parentid>719</parentid>
    <timestamp>2016-06-30T02:00:16Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24578" xml:space="preserve">''Well built library of valuable resources'''

The social media sensors (monitors) provided here a compiled list of the firm or supplier and the end prediction.


* * Social360 	Custom monitoring and reporting systems 	All 	www.social360monitoring.com 	Paid 	USA / UK / All 	www.social360monitoring.com 

* * BrandReact, Inc 	Social Media Monitoring, Reporting &amp; Response 	All: Blogs, News Sites, Consumer Sites (Radar, Kieskeurig etc), Review Sites (Yelp, Travelocity), Social Media (Facebook, Twitter, LinkedIn, YouTube, Orkut, Hyves, etc) 	http://BrandReact.net/brand 	Paid 	USA/Netherlands/Brasil 	Dick Raman 

* * iSentia Brandtology 	1-Social and Social Express 	All 	http://www.brandtology.com 	Paid 	USA, China, Hong Kong, Taiwan, Japan, Korea, Australia, Singapore, Malaysia, Indonesia, Thailand, Vietnam, India, New Zealand, Mexico, Brazil, France, Russia, Germany, Portugal, UK, Middle East 	Kelly Choo 

* * BrandProtect 	Social Media Monitoring, Reporting &amp; Incident Response Experts 	ALL 	BrandProtect 	Paid 	USA / Canada / UK 	Greg Barrow 

* * Needium 	Needium 	Twitter 	http://needium.com/ 	Paid 	USA, Canada, France, UK, more 	Sylvain Carle 

* * Dishy! AG 	ReputationTool 	All 	http://reputationtool.com 	Paid 	USA, Canada, Europe, Australia 	Ken Burbary 

* * Internet911 	Social Media: Understanding &amp; Protecting your Online Reputation for SMBs 	ALL 	Internet911 	Paid 	USA / Canada 	Greg Barrow 

* * Actionly 	Actionly 	Twitter, Facebook, Blogs, YouTube, Buzz, Flickr 	http://www.actionly.com 	Paid 	USA 	Actionly 

* * Ascent Labs, Inc. 	StatsMix 	All 	http://statsmix.com/ 	Free 	USA 	Sasha Kovaliov 

* * Asterisq 	Mentionmap 	Twitter 	http://apps.asterisq.com/mentionmap/# 	Free 	USA 	Bob Hodgson 

* * Attensity 	Market Voice 	All 	http://www.attensity.com 	Paid 	USA 	Ken Burbary 

* * Backtype 	Connect 	Blogs, Twitter, Friendfeed 	http://www.backtype.com/connect 	Free 	USA 	Ken Burbary 

* * Bantam Networks 	Bantam Live 	Twitter 	http://www.bantamlive.com/ 	Paid 	USA 	Bob Hodgson 

* * Betaworks 	Chartbear 	Twitter 	http://www.chartbeat.com 	Paid 	USA 	Nathan Folkman 

* * BitConfused 	BuzzDing 	All 	http://www.buzzding.com 	Paid 	USA 	Ken Burbary 

* * Bivings Group 	Impactwatch 	All 	http://impactwatch.com 	Paid 	USA 	Dave Murr 

* * Biz360 Inc. 	Biz360 	All 	Biz360 	Paid 	USA 	Len Kendall 

* * Buzzersation 	Buzzersation 	All 	http://www.buzzersation.com 	Paid 	USA 	Ken Burbary 

* * Buzzient 	Buzzient Enterprise 	All 	http://www.buzzient.com 	Paid 	USA 	Ken Burbary 

* * BuzzLogic 	BuzzLogic Insight 	All 	http://www.buzzlogic.com 	Paid 	USA 	Ken Burbary 

* * BuzzStream 	BuzzStream 	All 	http://www.buzzstream.com 	Free 	USA 	Ed Hartigan 

* * ChatterBeacon 	ChatterBeacon 	Facebook 	http://chatterbeacon.com 	Free 	USA 	Ken Burbary 

* * Cision 	Cision Social Media 	All 	http://us.cision.com/products_services/cision_social_media/overview.asp 	Paid 	USA 	Ken Burbary 

* * Collecta 	Collecta 	Micromedia, Blogs, Video 	Collecta.com 	Free 	USA 	Len Kendall 

* * Collective Intellect 	CI:View and CI:Insight 	All 	http://www.collectiveintellect.com 	Paid 	USA 	Ken Burbary 

* * Converseon 	Conversation Miner 	All 	http://www.converseon.com 	Paid 	USA 	Ken Burbary 

* * Conversition 	TweetFeel 	Twitter 	TweetFeel 	Free 	USA 	Len Kendall 

* * CoTweet 	CoTweet 	Twitter 	http://www.cotweet.com 	Free 	USA 	Ed Hartigan 

* * Crimson Hexagon 	Voxtrot 	All 	http://www.crimsonhexagon.com 	Paid 	USA 	Jay Baer 

* * Crowd Favorite 	Addictomatic 	All 	http://addictomatic.com 	Free 	USA 	Michelle Sullivan 

* * CustomScoop 	BuzzPerception 	Blogs 	http://www.customscoop.com 	Paid 	USA 	Chip Griffin 

* * CustomScoop 	ClipIQ 	All 	http://www.customscoop.com 	Paid 	USA 	Chip Griffin 

* * Cymfony 	Maestro 	All 	http://www.cymfony.com 	Paid 	USA 	Ken Burbary 

* * Cyveillance 	Cyveillance 	All 	http://www.cyveillance.com 	Paid 	USA 	Ken Burbary 

* * Decooda 	Decooda 	All 	http://decooda.com 	Paid 	USA 	Ken Burbary 

* * Digimind 	Digimind Meta-Search 	All 	http://www.digimind.com 	Paid 	USA 	Ken Burbary 

* * Dow Jones 	Dow Jones Insight 	All 	http://solutions.dowjones.com 	Paid 	USA 	Ken Burbary 

* * eCairn 	Conversation 	All 	http://www.ecairn.com 	Paid 	USA 	Ken Burbary 

* * Echometrix 	ThePulse 	All 	http://www.echometrix.com 	Paid 	USA 	Adam Smilowitz 

* * Effyis 	Boardreader 	Forums 	http://boardreader.com 	Free 	USA 	Ken Burbary 

* * Emerge Technology Group 	Socialscape 	All 	http://www.socialscape.biz 	Paid 	USA 	Ken Burbary 

* * EvoApp 	EvoApp 	All 	http://www.evoapp.com 	Paid 	USA 	Ken Burbary 

* * Facebook 	Search 	Facebook 	http://www.facebook.com/search 	Free 	USA 	Ken Burbary 

* * Facebook 	Lexicon 	Facebook 	http://www.facebook.com/lexicon 	Free 	USA 	Ken Burbary 

* * Glam Media 	Tinker 	Twitter 	http://www.tinker.com 	Free 	USA 	Ken Burbary 

* * Google 	Blogsearch 	Blogs 	http://blogsearch.google.com 	Free 	USA 	Ken Burbary 

* * GroupHigh 	GroupHigh 	Blogs 	http://www.grouphigh.com 	Paid 	USA 	Ken Burbary 

* * Hubspot 	Twitter Grader 	Twitter 	Twitter Grader 	Free 	USA 	Len Kendall 

* * Infegy 	Social Radar 	All 	Social Radar 	Paid 	USA 	Len Kendall 

* * Inifinimedia 	StartPR 	All 	http://startpr.com 	Paid 	USA 	Ken Burbary 

* * Insttant 	Insttant 	Twitter 	http://insttant.com 	Paid 	USA 	http://www.kenburbary.com 

* * Iterasi 	Positive Press 	All 	http://www.iterasi.net 	Paid 	USA 	Ken Burbary 

* * JD Power 	Umbria 	All 	http://www.jdpowerwebintelligence.com 	Paid 	USA 	Ken Burbary 

* * Jive Software 	Jive Social Media Engagement 	All 	http://www.jivesoftware.com 	Paid 	USA 	Ken Burbary 

* * Kaleidico 	Eavesdropper 	All 	http://kaleidico.com 	Paid 	USA 	Ken Burbary 

* * Kantar Video 	Videolytics 	Video 	http://www.kantarvideo.com 	Paid 	USA 	Ken Burbary 

* * Klout 	Klout 	Twitter 	http://klout.com 	Free 	USA 	Benjamin Schwarz 

* * Linkfluence 	Linkfluence 	All 	http://linkfluence.net 	Paid 	USA 	Ken Burbary 

* * ListenLogic 	Resonate 	All 	http://www.listenlogic.com 	Paid 	USA 	Ken Burbary 

* * Lithium Technologies 	Lithium Social Media Monitoring 	All 	http://www.lithium.com 	Paid 	USA 	Ken Burbary 

* * Looxii 	Looxii 	Social Media 	http://www.looxii.com/ 	Paid 	USA 	Alex Griffiths 

* * Loudpixel 	Loudpixel 		http://loudpixel.com/ 	Paid 	USA 	Alex Griffiths 

* * Martiz Research 	Evolve24 	The Mirror 	http://www.evolve24.com 	Paid 	USA 	Ken Burbary 

* * Medimix 	Scanbuzz 	All (niche - pharma) 	http://www.medimix.net/ 	Paid 	USA 	Ed Hartigan 

* * Meltwater 	Buzz 	All 	http://www.meltwater.com 	Paid 	USA 	Ken Burbary 

* * Meltwater Group 	BuzzGain 	All 	BuzzGain 	Paid 	USA 	Christine Fife 

* * Meltwater Group 	Icerocket 	Blogs 	http://www.icerocket.com 	Free 	USA 	Ken Burbary 

* * Meltwater Group 	JitterJam 	All 	http://www.jitterjam.com/ 	Paid 	USA 	E. Christopher Clark 

* * Milestone Internet Marketing 	eBuzz Connect 	All 	http://www.ebuzzconnect.com/ 	Paid 	USA 	Mike Supple 

* * Monitter 	Monitter 	Twitter 	http://www.monitter.com 	Free 	USA 	Ken Burbary 

* * Moreover Technologies 	Newsdesk 	All 	http://w.moreover.com 	Paid 	USA 	Ken Burbary 

* * MotiveQuest 	MotiveQuest 	All 	http://www.motivequest.com 	Paid 	USA 	Ken Burbary 

* * mReplay 	Livedash 	All 	http://www.livedash.com 	Free 	USA 	Ken Burbary 

* * NetBase 	ConsumerBase 	All 	http://www.netbase.com 	Paid 	USA 	Ken Burbary 

* * Networked Insights 	SocialSense 	All 	http://www.networkedinsights.com 	Paid 	USA 	Ken Burbary 

* * New Media Strategies 	AIM 	All 	http://newmediastrategies.net 	Paid 	USA 	Ken Burbary 

* * Nielsen 	Blogpulse 	Blogs 	http://www.blogpulse.com 	Free 	USA 	Ken Burbary 

* * Nielsen 	My BuzzMetrics 	All 	http://en-us.nielsen.com/tab/product_families/nielsen_buzzmetrics 	Paid 	USA 	Ken Burbary 

* * Now Metrix 	Trendrr 	All 	http://www.trendrr.com 	Free 	USA 	Ken Burbary 

* * NutShellMail 	NutShellMail 	Social Networks 	http://nutshellmail.com 	Free 	USA 	Ken Burbary 

* * OneRiot 	OneRiot 	Twitter, Digg, YouTube 	http://www.oneriot.com 	Free 	USA 	Ed Hartigan 

* * Overdrive Interactive 	Social Media Dashboard 	All 	http://www.ovrdrv.com 	Paid 	USA 	Jeff Selig 

* * Overtone 	Open Mic 	All 	http://www.overtone.com 	Paid 	USA 	Ed Hartigan 

* * PeopleBrowsr 	Analytic.ly 	All 	http://analytics.peoplebrowsr.com 	Paid 	USA 	Ken Burbary 

* * Pidgin Technologies 	Boardtracker 	Forums 	http://www.boardtracker.com 	Free 	USA 	Ken Burbary 

* * Position2 	Brand Monitor 	All 	Position2 Brand Monitor 	Paid 	USA 	Position2 

* * PR Newswire 	eWatch 	Blogs 	http://ewatch.prnewswire.com 	Paid 	USA 	Ken Burbary 

* * Raven 	Raven 	All 	Raven SEO Tools 	Paid 	USA 	Roy Morejon 

* * Reputation Defender 	Reputation Defender 	All 	http://www.reputationdefender.com 	Paid 	USA 	Ken Burbary 

* * ReputationHQ 	My Reputation Manager 	All 	http://reputationhq.com 	Paid 	USA 	Ken Burbary 

* * Reputationobserver 	Reputationobserver 	All 	http://www.reputationobserver.com 	Paid 	USA 	Sebastian 

* * ReviewIQ 	ReviewIQ 	All 	http://www.reviewiq.net 	Paid 	USA 	Ken Burbary 

* * Revinate 	Revinate 	All 	http://www.revinate.com 	Paid 	USA 	Ken Burbary 

* * RightNow 	RightNow CX 	All 	http://www.rightnow.com/ 	Paid 	USA 	Alex Griffiths 

* * Samepoint 	Samepoint 	All 	http://www.samepoint.com 	Free 	USA 	Ken Burbary 

* * Sensidea 	SocialSeek 	Blogs, Video, Micromedia, Photos 	SocialSeek 	Free 	USA 	Len Kendall 

* * SiteQuest Technologies 	Compliance WatchDog 	All 	http://www.sitequesttech.com 	Paid 	USA 	Ken Burbary 

* * Social Mention 	Social Mention 	All 	http://socialmention.com 	Free 	USA 	Ken Burbary 

* * SocialOomph 	SocialOomph 	Twitter 	SocialOomph 	Free 	USA 	Jason Mayes 

* * Spiral16 	Spark 	All 	http://www.spiral16.com 	Paid 	USA 	Ken Burbary 

* * Sports Media Challenge 	Buzz Manager  	All 	http://www.sportsmediachallenge.com/buzzmanager/index.html 	Paid 	USA 	Ryan Stephens 

* * Sprinklr 	Sprinklr 	Twitter and Facebook 	http://www.sprinklr.com/ 	Paid 	USA 	Christine Fife 

* * Sprout Social 	Sprout Social 	All 	http://sproutsocial.com/ 	Paid 	USA 	Alex Griffiths 

* * SWIX 	SWIX 	All 	http://swixhq.com/SWIX.html 	Paid 	USA 	Sasha Kovaliov 

* * Tealium 	Tealium SM 	All 	http://www.tealium.com/products/social-media/index.html 	Paid 	USA 	Tony Felice 

* * Technorati 	Blogsearch 	Blogs 	http://technorati.com 	Free 	USA 	Ken Burbary 

* * Techrigy 	SM2 	All 	http://www.alterian-social-media.com 	Paid 	USA 	Ken Burbary 

* * Telligent 	Telligent Analytics 	All 	http://telligent.com/products/telligent_analytics/ 	Paid 	USA 	Peter Brenchley 

* * The Search Monitor 	The Search Monitor (Starter and Pro) 	All 	http://www.thesearchmonitor.com/ 	Free 	USA 	Christine Fife 

* * TipTop Technologies 	TipTop 	Twitter, Amazon reviews 	http://feeltiptop.com 	Free 	USA 	Ken Burbary 

* * Todaypulse 	Todaypulse 	All 	http://todaypulse.com 	Paid 	USA 	Justin Walsh 

* * Topsy Labs 	Topsy 	Twitter 	http://topsy.com/ 	Free 	USA 	Christine Fife 

* * Trackur LLC. 	Trackur 	All 	Trackur 	Paid 	USA 	Roy Morejon 

* * Twazzup 	Twazzup 	Twitter 	http://www.twazzup.com 	Free 	USA 	Ken Burbary 

* * TweetBeep 	TweetBeep 	Twitter 	http://www.tweetbeep.com 	Free 	USA 	Michael Jensen 

* * Tweetlytics 	Tweetlytics 	Twitter 	http://www.tweetlytics.com/ 	Paid 	USA 	Alex Griffiths 

* * TweetReach 	TweetReach 	Twitter 	TweetReach 	Free 	USA 	Jason Mayes 

* * Twitter 	Twitter Search 	Twitter 	http://search .twitter.com 	Free 	USA 	Ken Burbary 

* * TwitterCounter 	TwitterCounter 	Twitter 	TwitterCounter 	Free 	USA 	Jason Mayes 

* * Viralheat 	Viralheat 	All 	http://www.viralheat.com 	Paid 	U.S.A 	Greg 

* * Visible Measures 	TruReach, Video Engagement 	Video 	http://www.visiblemeasures.com 	Paid 	USA 	Pierre-Loïc Assayag 

* * Visible Technologies 	Visible Intelligence 	All 	http://www.visibletechnologies.com 	Paid 	USA 	Ken Burbary 

* * Vocus, Inc. 	Vocus PR 	All 	http://www.vocus.com/content/social-media.asp 	Paid 	USA 	Ken Burbary 

* * Web Analytics Demystified 	Twitalyzer 	Twitter 	http://www.twitalyzer.com 	Free 	USA 	Ken Burbary 

* * Who's Talkin 	Who's Talkin 	ALL 	Who's Talkin 	Paid 	USA 	Roy Morejon 

* * Wildfire 	Monitor 	Twitter, Facebook 	http://monitor.wildfireapp.com 	Free 	USA 	Ken Burbary 

* * Wool.Labs 	WebDig, DigTV, AdSlider 	All Internet + TV/Radio 	http://woollabs.com 	Paid 	USA 	Steve Chiles 

* * Xerocity Design Group 	twitt(url)y 	Twitter 	http://twitturly.com/ 	Free 	USA 	Claudius Gerstner 

* * YackTrack 	YackTrack 	Blogs 	http://yacktrack.com 	Free 	USA 	Rob Diana 

* * MutualMind 	MutualMind 	All 	http://mutualmind.com 	Paid 	US 	Babar Bhatti 

* * Geofeedia 	Geofeedia 	Twitter, Instagram, Fickr, Picasa, YouTube 	http://www.geofeedia.com 	Paid 	United States 	Ken Burbary 

* * Social Agency Inc 	SpredFast 	All 	http://spredfast.com 	Paid 	United States 	Ken Burbary 

* * Social Report 	Social Report 	All 	https://www.socialreport.com 	Paid 	United States 	Ken Burbary 

* * DigitalMR  	Social Nuggets 	All 	http://www.digital-mr.com 	Paid 	UK, USA, Cyprus 	Michalis A. Michael 

* * Integrasco AS 	WoMPortal  	All 	Integrasco 	Paid 	UK, Norway, China 	Integrasco 

* * 1000Heads 	WOMTrak 	All 	http://www.1000heads.com 	Paid 	UK 	Ken Burbary 

* * Brandwatch 	Brandwatch 	All 	http://www.brandwatch.net 	Paid 	UK 	Fabrice Retkowsky 

* * Inuda Innovations 	HowSociable 	All 	http://howsociable.com/ 	Free 	UK 	Christine Fife 

* * Macranet 	Sentiment Metrics 	All 	http://www.sentimentmetrics.com 	Paid 	UK 	Ed Hartigan 

* * Market Sentinel 	LiveBuzz 	All 	http://www.marketsentinel.com/ 	Paid 	UK 	Christine Fife 

* * MediaBadger 	Mediasphere360 	All 	http://www.mediabadger.com 	Paid 	UK 	Ken Burbary 

* * Noteca 	Noteca 	All 	http://www.noteca.com 	Paid 	UK 	Ken Burbary 

* * Onalytica 	Direct Access - InfluenceMonitor 	All 	http://www.onalytica.com 	Paid 	UK 	Ken Burbary 

* * Rees Bradley Hepburn Ltd 	RBH Radar 	All 	http://www.rbh.co.uk 	Paid 	UK 	Ken Burbary 

* * Simpleweb Ltd. 	Media Genius 	All 	http://www.mediageniusapp.com 	Paid 	UK 	Ken Burbary 

* * Sodash 	Sodash 	Twitter, Facebook, email, specific blogs via RSS 	soda.sh/ 	Paid 	UK 	Alex Griffiths 

* * Tick Tock Boom Digital 	BoomSonar 	All 	http://www.boomsonar.com 	Paid 	Turkey 	Ken Burbary 

* * FinchLine 	FinchLine 	All 	http://www.finchline.nl 	Paid 	The Netherlands 	Ken Burbary 

* * New Music Labs BV 	Tribe Monitor 	Online (MySpace, Hyves, Last.fm, Twitter, Google Analytics, FaceBook, Google Video, Youtube) 	Tribe Monitor 	Free 	The Netherlands 	New Music Labs 

* * MeMo News AG 	MeMo News Monitoring 	All: News, Blogs, Forums, Social Media (Facebook, Twitter, Google+, Youtube ...) 	MeMoNews.com 	Paid 	Switzerland 	Stefan Vetter 

* * Netbreeze 	CommMonitor 	All 	http://www.netbreeze.ch 	Paid 	Switzerland 	Ken Burbary 

* * Intelliwell 	Informant 	All 	http://informant.se 	Paid 	Sweden 	Ken Burbary 

* * Patch6 AB 	Silverbakk Briefing Room 	All 	http://www.silverbakk.com 	Paid 	Sweden 	Ken Burbary 

* * Retriever  	Retriever 	Blogs, Twitter, Facebook 	http://www.retriever.se 	Paid 	Sweden 	Ken Burbary 

* * Cierzo Development S.L 	Smmart 	All 	http://www.smmart.es 	Paid 	Spain 	Ken Burbary 

* * Habber tec 	Social Web Intelligence 	All 	http://socialwebintelligence.com 	Paid 	Spain 	Ken Burbary 

* * Tinval Sistemes S.L. 	BrandChats 	All 	http://www.brandchats.com 	Paid 	Spain 	

* * WhatHashtag by Círculo Rojo 	WhatHashtag 	Twitter 	http://whathashtag.circulorojo.es/ 	Free 	Spain 	Álex Rubio @alexrbn (Círculo Rojo) 

* * Daumsoft 	UCCmetrics 	All 	http://www.daumsoft.com 	Paid 	South Korea 	Ken Burbary 

* * Brands Eye 	Brands Eye 	All 	http://www.brandseye.com 	Paid 	South Africa 	Ken Burbary 

* * ThoughtBuzz 	ThoughtBuzz 	All 	http://www.thoughtbuzz.net 	Paid 	Singapore, Malaysia, Philippines, Indonesia  	

* * JamIQ 	JamIQ 	All 	http://www.jamiq.com 	Paid 	Singapore 	

* * YouScan 	YouScan 	All 	http://www.youscan.ru 	Paid 	Russia, Ukraine 	Alexey Orap 

* * TreeWorks 	Zelist Monitor 	Blogs, Twitter, online media, Facebook, some of the most important discussion boards/forums in Romania 	http://www.zelistmonitor.ro 	Paid 	Romania 	Catalin Tenita 

* * BrandReact Nederland BV 	Social Media Monitoring, Reporting &amp; Response 	All: Blogs, News Sites, Consumer Sites (Radar, Kieskeurig etc), Review Sites (Yelp, Travelocity), Social Media (Facebook, Twitter, LinkedIn, YouTube, Orkut, Hyves, etc) 	BrandReact.NL 	Paid 	Netherlands, 
Belgium, Luxemburg 	Dick Raman 

* * Clipit News 	Clipit - online media monitoring 	All (dutch) 	http://www.clipit.nl 	Paid 	Netherlands 	Sjaak Janssen 

* * iMonitoring 	iMonitoring 	All 	http://www.internetmonitoring.nl 	Paid 	Netherlands 	Ken Burbary 

* * Teezir  	eCare 	All 	http://www.teezir.com 	Paid 	Netherlands 	Ken Burbary 

* * TraceBuzz 	TraceBuzz 	All 	http://www.tracebuzz.com 	Paid 	Netherlands 	Ken Burbary 

* * Twitter Analyzer 	Twitter Analyzer 	Twitter 	http://twitteranalyzer.com 	Free 	Netherlands 	Claudius Gerstner 

* * Trendiction 	Trendiction Search 	All 	http://www.trendiction.com 	Paid 	Luxembourg 	Ken Burbary 

* * Expert System 	Cognito Monitor 	All 	http://www.expertsystem.net 	Paid 	Italy, USA 	Ken Burbary 

* * BuzzDetector 	BuzzDetector 	All 	http://www.buzzdetector.com 	Paid 	Italy 	Ken Burbary 

* * infoFactory 	ifMONITOR 	All 	http://www.infofactory.it 	Paid 	Italy 	Ken Burbary 

* * SocialPointer 	Social Pointer 	All 	http://www.socialpointer.com 	Free 	Israel 	Yair Benyami 

* * Katapedia 	Katapedia 	All 	http://www.katapedia.com 	Paid 	Indonesia 	Deddy Rahman 

* * Beevolve 	Social Media Monitoring &amp; Engagement Platform 	All 	http://www.beevolve.com/ 	Paid 	India 	Christine Fife 

* * Factualz 	Factualz 	All 	http://www.factualz.com 	Paid 	India 	Ken Burbary 

* * Omllion 	Omllion 	All 	http://www.omllion.com 	Paid 	India 	Ken Burbary 

* * Webfluenz  	Webfluenz  	All 	http://webfluenz.com 	Paid 	India 	Ken Burbary 

* * Brandmonitor 	Brandmonitor 	All 	http://www.brandmonitor.hu 	Paid 	Hungary 	

* * Glerts 	Glerts 	All media indexed by Google 	http://www.glerts.com/beta 	Free 	Global 	http://www.glert.com 

* * Cognita AG 	blueReport 	Blogs, Twitter 	http://www.bluereport.net 	Paid 	Germany, Switzerland, Austria  	Ken Burbary 

* * Mindlab Solutions GmbH 	netmind Sphere 	All 	http://www.mindlab.de 	Paid 	Germany, Austria, Switzerland 	Heinz D. Schultz 

* * Ethority 	Gridmaster 	All 	http://www.ethority.net 	Paid 	Germany 	Ken Burbary 

* * Frank Westphal 	Rivva 	Blogs, Twitter 	http://rivva.de/ 	Free 	Germany 	Claudius Gerstner 

* * iMooty 	iMooty 	News 	http://www.imooty.eu 	Free 	Germany 	Ken Burbary 

* * infospeed 	web2monitor™ 	All 	infospeed 	Paid 	Germany 	Social Media Magazin 

* * Landau Media 	Landau Media Monitoring Internet 	All 	http://www.landaumedia.de 	Paid 	Germany 	Ken Burbary 

* * net-clipping 	net-clipping 	Online, Social Media, amazon, facebook 	http://net-clipping.de 	Paid 	Germany 	Cornelia Horst 

* * New Communication 	Reputation Control 	All 	http://www.reputation-control.de 	Paid 	Germany 	

* * TwentyFeet 	TwentyFeet 	Twitter, Facebook, YouTube, Google Analytics, bit.ly, MySpace 	http://www.twentyfeet.com 	Paid 	Germany 	Paul Herwarth 

* * User Interface Design GmbH 	What's Up?! 	Twitter 	http://whatsup.uid.com 	Free 	Germany 	Ken Burbary 

* * Webbosaurus 	Webboboard 	All 	webbosaurus.de 	Paid 	Germany 	Webbosaurus 

* * AT Internet 	BuzzWatcher 	All 	http://en.atinternet.com 	Paid 	France 	Ken Burbary 

* * AT Internet 	BuzzWatcher 	All 	http://en.atinternet.com/Products/BuzzWatcher.aspx 	Paid 	France 	Ken Burbary 

* * Semiocast 	Semioboard 	All 	Semioboard.com 	Paid 	France 	Jean-Charles Campagne 

* * Statsit  	Monitor 	All 	http://www.statsit.com 	Paid 	Finland, Malaysia 	Ken Burbary 

* * M-Brain 	M-Brain 	All 	http://www.m-brain.com/ 	Paid 	Finland 	Joakim Nyberg 

* * Whitevector 	Whitevector 	All 	http://www.whitevector.com 	Paid 	Finland 	Ken Burbary 

* * Blogmeter 	Blogmeter 	All 	http://www.blogmeter.eu 	Paid 	Europe 	Barbara Aversano 

* * Replise 	Replise 	All 	Replise.com 	Paid 	Europe 	

* * Socialware 	Asomo 	All 	http://www.asomo.net 	Paid 	Europe 	Ken Burbary 

* * Synthesio 	Synthesio 	All 	Synthesio 	Paid 	Europe 	Len Kendall 

* * BrandMetric 	BrandMetric 	All 	http://www.brandmetric.com 	Paid 	Chile 	Ken Burbary 

* * DNA13 	dnaMonitor 	All 	http://www.dna13.com/ 	Paid 	Canada 	Christine Fife 

* * Lola 	Variety of off-the-shelf tools and proprietary technologies 	All online sources 	Lola 	Paid 	Canada 	Luis Vieira 

* * MediaMiser 	MediaMiser Enterprise 	All 	http://www.mediamiser.com 	Paid 	Canada 	Ken Burbary 

* * MyFrontSteps 	Steprep 	All 	http://steprep.myfrontsteps.com 	Free 	Canada 	Ken Burbary 

* * PostRank Inc 	PostRank 	RSS Enabled Content, Blogs, Social Networks &amp; Hubs 	PostRank 	Free 	Canada 	PostRank 

* * RepuMetrix 	RepuTrace, RepuTrack 	All 	http://www.repumetrix.com 	Paid 	Canada 	Ken Burbary 

* * Salesforce 	Radian6 	All 	http://www.radian6.com 	Paid 	Canada 	Ken Burbary 

* * Syncapse Corp 	Socialtalk 	Twitter, Facebook, Wordpress, Moveable Type 	http://www.socialtalk.com 	Paid 	Canada 	Alex Griffiths 

* * Sysomos 	MAP, Heartbeat 	All 	http://www.sysomos.com 	Paid 	Canada 	Ken Burbary 

* * White Noise Inc. 	White Noise 	All 	http://www.herdthenoise.com 	Paid 	Canada 	Ken Burbary 

* * Chleba Agencia digital 	Social media Monitor 	Google Blogs / Flickr / Twitter / Google News / Yahoo Respostas / Facebook / Orkut Comunidades / Reclame Aqui / YouTube  	http://www.socialmediamonitor.com.br/ 	Paid 	Brazil 	Henrique Rangel 

* * Scup 	Scup 	All 	http://www.scup.com.br 	Paid 	Brazil 	Ken Burbary 

* * Attentio 	Buzz Report 	All 	http://www.attentio.com 	Paid 	Belgium 	Simon McDermott 

* * BrandFractal  	CommandCenter, Sodalyzer, social data analytics 	All 	http://www.brandfractal.com 	Paid 	Belgium 	Ken Burbary 

* * Engagor 	Engagor Insights 	All 	http://www.engagor.com 	Paid 	Belgium 	Ken Burbary 

* * BuzzNumbers 	BuzzNumbers 	All 	http://www.buzznumbershq.com 	Paid 	Australia 	Ken Burbary 

* * e-CBD 	Dialogix 	All 	http://www.dpdialogue.com.au 	Paid 	Australia 	Ken Burbary 

* * StreamWall 	StreamWall 	All 	http://www.socialmediamonitoring.com.au 	Paid 	Australia 	Ken Burbary 

* * Walkley 	Walkley 	All 	http://www.walkley.com.au/ 	Paid 	Australia 	Walkley 

* * Flaptor 	Trendistic (formerly Twist) 	Twitter 	http://trendistic.com 	Free 	Argentina 	Claudius Gerstner 

* * SocialMetrix 	SocialMetrix 	All 	http://www.SocialMetrix.com 	Paid 	Argentina 	Sebastian Rosenfeld 

* * Buzzcapture B.V. 	Buzzcapture 	All 	http://www.buzzcapture.com 	Paid 	Amsterdam 	Ken Burbary 

* * Eurospider Information Technology AG 	Media Monitoring &amp; Management 	All 	Media Monitoring &amp;amp; Management 	Paid 	All 	Loig Roumois 

* * uberVU 	uberVU 	blogs, Twitter, Digg, FriendFeed and many more 	http://www.ubervu.com/ 	Free 		Bryan Skelton 

* * WhoUnfollowedMe 	WhoUnfollowedMe 	Twitter 	WhoUnfollowedMe 	Free 		Jason Mayes 

[[Category:OSINT]]</text>
    <sha1>778a7e4333164dc91b407e8782ec12929aa8042f</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>File:Open Source Intelligence Professional Handbook.pdf</title>
  <ns>6</ns>
  <id>301</id>
  <revision>
    <id>720</id>
    <timestamp>2016-06-30T01:45:48Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>721</id>
    <parentid>720</parentid>
    <timestamp>2016-06-30T01:51:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22" xml:space="preserve">[[Category:Resources]]</text>
    <sha1>8e670026d35cdefe0315772d2adb5392b9928605</sha1>
  </revision>
  <revision>
    <id>722</id>
    <parentid>721</parentid>
    <timestamp>2016-06-30T01:52:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">[[Category:OSINT Resources]]</text>
    <sha1>5d3310acf15f2ef6cf0b5c8b88bcaa376510a0e8</sha1>
  </revision>
  <revision>
    <id>723</id>
    <parentid>722</parentid>
    <timestamp>2016-06-30T01:52:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">[[Category:OSINT]]</text>
    <sha1>1deef907935ff6f6149fc1160398190635d9d7f0</sha1>
  </revision>
  <revision>
    <id>727</id>
    <parentid>723</parentid>
    <timestamp>2016-06-30T02:02:05Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="41" xml:space="preserve">[[Category:Resources]]
[[Category:OSINT]]</text>
    <sha1>1c74451b963a34b81cdb653fa360a111e68afe5d</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>File:Benavides Online OSINT Quick Reference Handbook 2009.epub</title>
  <ns>6</ns>
  <id>302</id>
  <revision>
    <id>724</id>
    <timestamp>2016-06-30T01:54:09Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>725</id>
    <parentid>724</parentid>
    <timestamp>2016-06-30T01:54:33Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">[[Category:OSINT]]</text>
    <sha1>1deef907935ff6f6149fc1160398190635d9d7f0</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>File:Reachback-Operations-for-Air-Campaign-Planning-and-Execution.pdf</title>
  <ns>6</ns>
  <id>303</id>
  <revision>
    <id>728</id>
    <timestamp>2016-06-30T02:26:28Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>729</id>
    <parentid>728</parentid>
    <timestamp>2016-06-30T02:27:46Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[File:Csat1.pdf]] to [[File:Reachback-Operations-for-Air-Campaign-Planning-and-Execution.pdf]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>730</id>
    <parentid>729</parentid>
    <timestamp>2016-06-30T02:28:20Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22" xml:space="preserve">[[Category:Reference]]</text>
    <sha1>2c7e43280fb308c1445a5efa4ab771563762b9c7</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>Knowledge Center</title>
  <ns>0</ns>
  <id>200</id>
  <revision>
    <id>731</id>
    <parentid>617</parentid>
    <timestamp>2016-06-30T02:33:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="583" xml:space="preserve">__NOEDITSECTION__
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |

|}
|}


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>320ac3becf86ce4e12f0a428bac8c2747059b604</sha1>
  </revision>
  <revision>
    <id>732</id>
    <parentid>731</parentid>
    <timestamp>2016-06-30T02:34:13Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Undo revision 731 by [[Special:Contributions/Eddie|Eddie]] ([[User talk:Eddie|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="582" xml:space="preserve">__NOEDITSECTION__
[[File:World-Banner.png|left|framed|link= ]]
{| style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

&lt;!--        "WELCOME TO OWIKI AND ARTICLE COUNT        --&gt;
{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
&lt;div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"&gt;REACHBACK OPERATIONS
&lt;/div&gt;
|}
|}


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>21e5f0a2737b63ed9e5292408193246bac0742b9</sha1>
  </revision>
  <revision>
    <id>733</id>
    <parentid>732</parentid>
    <timestamp>2016-06-30T02:49:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4560" xml:space="preserve">__NOTOC__ __NOEDITSECTION__
=Overview=

This site provides a working prototype for a reachback support cell. 

'''Situation Center'''  This provides an automated analysis of certain data that is being collected during the assessment. This utilizes a two part process, first data is collected, it is then formatted and analyzed by back end systems.

'''Progress Status'''  Updates on current, completed, and upcoming activities.

'''Risk factors''' Additional elements that have been uncovered and are being considered during the assessment.

=Alert Level=


=Situation Center=

{|
|style="vertical-align:top"|{{#viki:pageTitles=Current Activities, Surface Exposure|width=500|height=500}}
|}

=Progress Status=

{|-
| style="color:#000;padding:2px 3px 3px" | &lt;div&gt;
&lt;br /&gt;
  '''[[MediaWiki:Overarching|Overarching]]''' Guiding Instruments
  * Center of Gravity
  * '''[[Crown Jewels Analysis]]'''
  * Targeting Assessment Countering Analysis (TCAC)
  * '''[[Cyber Early Warning|Cyber Threats]]''' and '''[[ABI-INTRO|methodology]]'''
&lt;/div&gt;
|}

''' Complete '''
&lt;br /&gt;
* Deployment into the reachback.io as the primary family
 MOBOPS namespace included as family member
 MOBOPS namespace interlink translation to CIMACELL extended family
* Custom monitoring for information leaks (paste sites, TOR to clear dump links etc.)
* Passive sensor placements (DNS)
* Harvesting agent placements (Surface Exposure and Targeting)
* Established links to allow emerging associations and pattern analysis 

''' Ongoing '''
* Defining Centers of Gravity 
* Global Awareness - provide awareness of the current landscape.
* Threat  Analysis - a semantic based analytically living product.. 
* Surface Exposure - visually representation showing the surface exposure to pinpoint areas of interest and support in minimizing.
* Identifying domains, websites, and dns and other online assets with a direct relationship]
* Identifying third parties, trusted business partners, vendors, and others indirect relationships 
* Learning the people, personalities, and positions within the organization to assess their ability to help obtain access.
* Learning the technology and internal structure and staff responsible for the various areas the technology is used.
* Multi discipline intelligence activities
* Link analysis, historical timeline, and social network analysis using online social network media

=Risk Factors=

&lt;br /&gt;
The methodology used in risk and vulnerability analysis was developed to compliment the best practices found in fortune 50 organizations, and organizations like MITRE.  Our hybrid solution is unique both in the innovative use of technology and in our counter target centric approach.
&lt;br /&gt;
{{New Paragraph}}
&lt;big&gt;''' Third Parties '''&lt;/big&gt;
&lt;br /&gt;
Other organizations who deal with Motability data and therefore may pose a third party risk.
* httx://www.rsagroup.com/rsagroup/en/home Royal Sun Alliance Insurance
* httx://www.rac.co.uk/new The RAC
* httxs://www.kwik-fit.com/home.asp Kwik Fit
{{New Paragraph}}
&lt;big&gt;''' Computer Networks '''&lt;/big&gt;
&lt;br /&gt;
[[IPV4_info|MOBOPS Identified IP addresses]]
&lt;br /&gt;
[[Certificates|Digital Certificates]]
{{New Paragraph}}
&lt;big&gt;'''Open Source'''&lt;/big&gt;
*Associated domains - 30+ direct 10+ indirect - note this is not an effort to identify MOBOPS “owned assets” but rather MOBOPS “assets to protect” and the accepting risks resulting from outside or uncontrollable through normal risk management processes.  
*Associated email accounts - 30+ high value accounts that could be used as part of an attack plan. 
*Associated technologies - Video appears to be of interest but for purposes not directly obvious for use in attack.  Our team will continue to identify the interest and initially make attempts to determine any covert communications directly related to an attack and providing command and control (C2) functions and the possible manipulation by third parties for their benefit.     
*Social Media - we have started to look into the social media practices of MOBOPS for comparison with research datasets.  Our services are focused in sentiment analysis, influence, rumor analysis, and deception detection and deceptive countermeasures for protection.  If there are requirements or desires for social media monitoring or trend analysis we have an extensive list of providers and services ranging from free to geared for government pricing that can be accessed for assisting in such areas.

&lt;headertabs /&gt;

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>235002d20f16e54b4e26afd9c79c079b16d14e41</sha1>
  </revision>
  <revision>
    <id>734</id>
    <parentid>733</parentid>
    <timestamp>2016-06-30T03:00:56Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4558" xml:space="preserve">__NOTOC__ __NOEDITSECTION__
=Overview=

This site provides working prototype for a reachback support cell. 

'''Situation Center'''  This provides an automated analysis of certain data that is being collected during the assessment. This utilizes a two part process, first data is collected, it is then formatted and analyzed by back end systems.

'''Progress Status'''  Updates on current, completed, and upcoming activities.

'''Risk factors''' Additional elements that have been uncovered and are being considered during the assessment.

=Alert Level=


=Situation Center=

{|
|style="vertical-align:top"|{{#viki:pageTitles=Current Activities, Surface Exposure|width=500|height=500}}
|}

=Progress Status=

{|-
| style="color:#000;padding:2px 3px 3px" | &lt;div&gt;
&lt;br /&gt;
  '''[[MediaWiki:Overarching|Overarching]]''' Guiding Instruments
  * Center of Gravity
  * '''[[Crown Jewels Analysis]]'''
  * Targeting Assessment Countering Analysis (TCAC)
  * '''[[Cyber Early Warning|Cyber Threats]]''' and '''[[ABI-INTRO|methodology]]'''
&lt;/div&gt;
|}

''' Complete '''
&lt;br /&gt;
* Deployment into the reachback.io as the primary family
 MOBOPS namespace included as family member
 MOBOPS namespace interlink translation to CIMACELL extended family
* Custom monitoring for information leaks (paste sites, TOR to clear dump links etc.)
* Passive sensor placements (DNS)
* Harvesting agent placements (Surface Exposure and Targeting)
* Established links to allow emerging associations and pattern analysis 

''' Ongoing '''
* Defining Centers of Gravity 
* Global Awareness - provide awareness of the current landscape.
* Threat  Analysis - a semantic based analytically living product.. 
* Surface Exposure - visually representation showing the surface exposure to pinpoint areas of interest and support in minimizing.
* Identifying domains, websites, and dns and other online assets with a direct relationship]
* Identifying third parties, trusted business partners, vendors, and others indirect relationships 
* Learning the people, personalities, and positions within the organization to assess their ability to help obtain access.
* Learning the technology and internal structure and staff responsible for the various areas the technology is used.
* Multi discipline intelligence activities
* Link analysis, historical timeline, and social network analysis using online social network media

=Risk Factors=

&lt;br /&gt;
The methodology used in risk and vulnerability analysis was developed to compliment the best practices found in fortune 50 organizations, and organizations like MITRE.  Our hybrid solution is unique both in the innovative use of technology and in our counter target centric approach.
&lt;br /&gt;
{{New Paragraph}}
&lt;big&gt;''' Third Parties '''&lt;/big&gt;
&lt;br /&gt;
Other organizations who deal with Motability data and therefore may pose a third party risk.
* httx://www.rsagroup.com/rsagroup/en/home Royal Sun Alliance Insurance
* httx://www.rac.co.uk/new The RAC
* httxs://www.kwik-fit.com/home.asp Kwik Fit
{{New Paragraph}}
&lt;big&gt;''' Computer Networks '''&lt;/big&gt;
&lt;br /&gt;
[[IPV4_info|MOBOPS Identified IP addresses]]
&lt;br /&gt;
[[Certificates|Digital Certificates]]
{{New Paragraph}}
&lt;big&gt;'''Open Source'''&lt;/big&gt;
*Associated domains - 30+ direct 10+ indirect - note this is not an effort to identify MOBOPS “owned assets” but rather MOBOPS “assets to protect” and the accepting risks resulting from outside or uncontrollable through normal risk management processes.  
*Associated email accounts - 30+ high value accounts that could be used as part of an attack plan. 
*Associated technologies - Video appears to be of interest but for purposes not directly obvious for use in attack.  Our team will continue to identify the interest and initially make attempts to determine any covert communications directly related to an attack and providing command and control (C2) functions and the possible manipulation by third parties for their benefit.     
*Social Media - we have started to look into the social media practices of MOBOPS for comparison with research datasets.  Our services are focused in sentiment analysis, influence, rumor analysis, and deception detection and deceptive countermeasures for protection.  If there are requirements or desires for social media monitoring or trend analysis we have an extensive list of providers and services ranging from free to geared for government pricing that can be accessed for assisting in such areas.

&lt;headertabs /&gt;

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>97928e6eee673d29823530c356a195b6d1ea0c83</sha1>
  </revision>
  <revision>
    <id>740</id>
    <parentid>734</parentid>
    <timestamp>2016-06-30T04:22:31Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4537" xml:space="preserve">__NOTOC__ __NOEDITSECTION__
=Overview=

[[File:Reachback-def-jp-3-30.png|framed|left]]

'''Situation Center'''  This provides an automated analysis of certain data that is being collected during the assessment. This utilizes a two part process, first data is collected, it is then formatted and analyzed by back end systems.

'''Progress Status'''  Updates on current, completed, and upcoming activities.

'''Risk factors''' Additional elements that have been uncovered and are being considered during the assessment.

=Alert Level=


=Situation Center=

{|
|style="vertical-align:top"|{{#viki:pageTitles=Current Activities, Surface Exposure|width=500|height=500}}
|}

=Progress Status=

{|-
| style="color:#000;padding:2px 3px 3px" | &lt;div&gt;
&lt;br /&gt;
  '''[[MediaWiki:Overarching|Overarching]]''' Guiding Instruments
  * Center of Gravity
  * '''[[Crown Jewels Analysis]]'''
  * Targeting Assessment Countering Analysis (TCAC)
  * '''[[Cyber Early Warning|Cyber Threats]]''' and '''[[ABI-INTRO|methodology]]'''
&lt;/div&gt;
|}

''' Complete '''
&lt;br /&gt;
* Deployment into the reachback.io as the primary family
 MOBOPS namespace included as family member
 MOBOPS namespace interlink translation to CIMACELL extended family
* Custom monitoring for information leaks (paste sites, TOR to clear dump links etc.)
* Passive sensor placements (DNS)
* Harvesting agent placements (Surface Exposure and Targeting)
* Established links to allow emerging associations and pattern analysis 

''' Ongoing '''
* Defining Centers of Gravity 
* Global Awareness - provide awareness of the current landscape.
* Threat  Analysis - a semantic based analytically living product.. 
* Surface Exposure - visually representation showing the surface exposure to pinpoint areas of interest and support in minimizing.
* Identifying domains, websites, and dns and other online assets with a direct relationship]
* Identifying third parties, trusted business partners, vendors, and others indirect relationships 
* Learning the people, personalities, and positions within the organization to assess their ability to help obtain access.
* Learning the technology and internal structure and staff responsible for the various areas the technology is used.
* Multi discipline intelligence activities
* Link analysis, historical timeline, and social network analysis using online social network media

=Risk Factors=

&lt;br /&gt;
The methodology used in risk and vulnerability analysis was developed to compliment the best practices found in fortune 50 organizations, and organizations like MITRE.  Our hybrid solution is unique both in the innovative use of technology and in our counter target centric approach.
&lt;br /&gt;
{{New Paragraph}}
&lt;big&gt;''' Third Parties '''&lt;/big&gt;
&lt;br /&gt;
Other organizations who deal with Motability data and therefore may pose a third party risk.
* httx://www.rsagroup.com/rsagroup/en/home Royal Sun Alliance Insurance
* httx://www.rac.co.uk/new The RAC
* httxs://www.kwik-fit.com/home.asp Kwik Fit
{{New Paragraph}}
&lt;big&gt;''' Computer Networks '''&lt;/big&gt;
&lt;br /&gt;
[[IPV4_info|MOBOPS Identified IP addresses]]
&lt;br /&gt;
[[Certificates|Digital Certificates]]
{{New Paragraph}}
&lt;big&gt;'''Open Source'''&lt;/big&gt;
*Associated domains - 30+ direct 10+ indirect - note this is not an effort to identify MOBOPS “owned assets” but rather MOBOPS “assets to protect” and the accepting risks resulting from outside or uncontrollable through normal risk management processes.  
*Associated email accounts - 30+ high value accounts that could be used as part of an attack plan. 
*Associated technologies - Video appears to be of interest but for purposes not directly obvious for use in attack.  Our team will continue to identify the interest and initially make attempts to determine any covert communications directly related to an attack and providing command and control (C2) functions and the possible manipulation by third parties for their benefit.     
*Social Media - we have started to look into the social media practices of MOBOPS for comparison with research datasets.  Our services are focused in sentiment analysis, influence, rumor analysis, and deception detection and deceptive countermeasures for protection.  If there are requirements or desires for social media monitoring or trend analysis we have an extensive list of providers and services ranging from free to geared for government pricing that can be accessed for assisting in such areas.

&lt;headertabs /&gt;

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>2079a15e2dfb99e43751ae3563bae850e160fda9</sha1>
  </revision>
  <revision>
    <id>741</id>
    <parentid>740</parentid>
    <timestamp>2016-06-30T04:23:10Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4526" xml:space="preserve">__NOTOC__ __NOEDITSECTION__

[[File:Reachback-def-jp-3-30.png|framed|left]]

'''Situation Center'''  This provides an automated analysis of certain data that is being collected during the assessment. This utilizes a two part process, first data is collected, it is then formatted and analyzed by back end systems.

'''Progress Status'''  Updates on current, completed, and upcoming activities.

'''Risk factors''' Additional elements that have been uncovered and are being considered during the assessment.

=Alert Level=


=Situation Center=

{|
|style="vertical-align:top"|{{#viki:pageTitles=Current Activities, Surface Exposure|width=500|height=500}}
|}

=Progress Status=

{|-
| style="color:#000;padding:2px 3px 3px" | &lt;div&gt;
&lt;br /&gt;
  '''[[MediaWiki:Overarching|Overarching]]''' Guiding Instruments
  * Center of Gravity
  * '''[[Crown Jewels Analysis]]'''
  * Targeting Assessment Countering Analysis (TCAC)
  * '''[[Cyber Early Warning|Cyber Threats]]''' and '''[[ABI-INTRO|methodology]]'''
&lt;/div&gt;
|}

''' Complete '''
&lt;br /&gt;
* Deployment into the reachback.io as the primary family
 MOBOPS namespace included as family member
 MOBOPS namespace interlink translation to CIMACELL extended family
* Custom monitoring for information leaks (paste sites, TOR to clear dump links etc.)
* Passive sensor placements (DNS)
* Harvesting agent placements (Surface Exposure and Targeting)
* Established links to allow emerging associations and pattern analysis 

''' Ongoing '''
* Defining Centers of Gravity 
* Global Awareness - provide awareness of the current landscape.
* Threat  Analysis - a semantic based analytically living product.. 
* Surface Exposure - visually representation showing the surface exposure to pinpoint areas of interest and support in minimizing.
* Identifying domains, websites, and dns and other online assets with a direct relationship]
* Identifying third parties, trusted business partners, vendors, and others indirect relationships 
* Learning the people, personalities, and positions within the organization to assess their ability to help obtain access.
* Learning the technology and internal structure and staff responsible for the various areas the technology is used.
* Multi discipline intelligence activities
* Link analysis, historical timeline, and social network analysis using online social network media

=Risk Factors=

&lt;br /&gt;
The methodology used in risk and vulnerability analysis was developed to compliment the best practices found in fortune 50 organizations, and organizations like MITRE.  Our hybrid solution is unique both in the innovative use of technology and in our counter target centric approach.
&lt;br /&gt;
{{New Paragraph}}
&lt;big&gt;''' Third Parties '''&lt;/big&gt;
&lt;br /&gt;
Other organizations who deal with Motability data and therefore may pose a third party risk.
* httx://www.rsagroup.com/rsagroup/en/home Royal Sun Alliance Insurance
* httx://www.rac.co.uk/new The RAC
* httxs://www.kwik-fit.com/home.asp Kwik Fit
{{New Paragraph}}
&lt;big&gt;''' Computer Networks '''&lt;/big&gt;
&lt;br /&gt;
[[IPV4_info|MOBOPS Identified IP addresses]]
&lt;br /&gt;
[[Certificates|Digital Certificates]]
{{New Paragraph}}
&lt;big&gt;'''Open Source'''&lt;/big&gt;
*Associated domains - 30+ direct 10+ indirect - note this is not an effort to identify MOBOPS “owned assets” but rather MOBOPS “assets to protect” and the accepting risks resulting from outside or uncontrollable through normal risk management processes.  
*Associated email accounts - 30+ high value accounts that could be used as part of an attack plan. 
*Associated technologies - Video appears to be of interest but for purposes not directly obvious for use in attack.  Our team will continue to identify the interest and initially make attempts to determine any covert communications directly related to an attack and providing command and control (C2) functions and the possible manipulation by third parties for their benefit.     
*Social Media - we have started to look into the social media practices of MOBOPS for comparison with research datasets.  Our services are focused in sentiment analysis, influence, rumor analysis, and deception detection and deceptive countermeasures for protection.  If there are requirements or desires for social media monitoring or trend analysis we have an extensive list of providers and services ranging from free to geared for government pricing that can be accessed for assisting in such areas.

&lt;headertabs /&gt;

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>91626c354a051dfdb7b5f64aa3b48abcd9c3b330</sha1>
  </revision>
  <revision>
    <id>742</id>
    <parentid>741</parentid>
    <timestamp>2016-06-30T04:23:49Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4088" xml:space="preserve">__NOTOC__ __NOEDITSECTION__

[[File:Reachback-def-jp-3-30.png|framed|left]]

&lt;br /&gt;


=Situation Center=

{|
|style="vertical-align:top"|{{#viki:pageTitles=Current Activities, Surface Exposure|width=500|height=500}}
|}

=Progress Status=

{|-
| style="color:#000;padding:2px 3px 3px" | &lt;div&gt;
&lt;br /&gt;
  '''[[MediaWiki:Overarching|Overarching]]''' Guiding Instruments
  * Center of Gravity
  * '''[[Crown Jewels Analysis]]'''
  * Targeting Assessment Countering Analysis (TCAC)
  * '''[[Cyber Early Warning|Cyber Threats]]''' and '''[[ABI-INTRO|methodology]]'''
&lt;/div&gt;
|}

''' Complete '''
&lt;br /&gt;
* Deployment into the reachback.io as the primary family
 MOBOPS namespace included as family member
 MOBOPS namespace interlink translation to CIMACELL extended family
* Custom monitoring for information leaks (paste sites, TOR to clear dump links etc.)
* Passive sensor placements (DNS)
* Harvesting agent placements (Surface Exposure and Targeting)
* Established links to allow emerging associations and pattern analysis 

''' Ongoing '''
* Defining Centers of Gravity 
* Global Awareness - provide awareness of the current landscape.
* Threat  Analysis - a semantic based analytically living product.. 
* Surface Exposure - visually representation showing the surface exposure to pinpoint areas of interest and support in minimizing.
* Identifying domains, websites, and dns and other online assets with a direct relationship]
* Identifying third parties, trusted business partners, vendors, and others indirect relationships 
* Learning the people, personalities, and positions within the organization to assess their ability to help obtain access.
* Learning the technology and internal structure and staff responsible for the various areas the technology is used.
* Multi discipline intelligence activities
* Link analysis, historical timeline, and social network analysis using online social network media

=Risk Factors=

&lt;br /&gt;
The methodology used in risk and vulnerability analysis was developed to compliment the best practices found in fortune 50 organizations, and organizations like MITRE.  Our hybrid solution is unique both in the innovative use of technology and in our counter target centric approach.
&lt;br /&gt;
{{New Paragraph}}
&lt;big&gt;''' Third Parties '''&lt;/big&gt;
&lt;br /&gt;
Other organizations who deal with Motability data and therefore may pose a third party risk.
* httx://www.rsagroup.com/rsagroup/en/home Royal Sun Alliance Insurance
* httx://www.rac.co.uk/new The RAC
* httxs://www.kwik-fit.com/home.asp Kwik Fit
{{New Paragraph}}
&lt;big&gt;''' Computer Networks '''&lt;/big&gt;
&lt;br /&gt;
[[IPV4_info|MOBOPS Identified IP addresses]]
&lt;br /&gt;
[[Certificates|Digital Certificates]]
{{New Paragraph}}
&lt;big&gt;'''Open Source'''&lt;/big&gt;
*Associated domains - 30+ direct 10+ indirect - note this is not an effort to identify MOBOPS “owned assets” but rather MOBOPS “assets to protect” and the accepting risks resulting from outside or uncontrollable through normal risk management processes.  
*Associated email accounts - 30+ high value accounts that could be used as part of an attack plan. 
*Associated technologies - Video appears to be of interest but for purposes not directly obvious for use in attack.  Our team will continue to identify the interest and initially make attempts to determine any covert communications directly related to an attack and providing command and control (C2) functions and the possible manipulation by third parties for their benefit.     
*Social Media - we have started to look into the social media practices of MOBOPS for comparison with research datasets.  Our services are focused in sentiment analysis, influence, rumor analysis, and deception detection and deceptive countermeasures for protection.  If there are requirements or desires for social media monitoring or trend analysis we have an extensive list of providers and services ranging from free to geared for government pricing that can be accessed for assisting in such areas.

&lt;headertabs /&gt;

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>a3cf43de79820cabb5de3f1291f025856eb5ab8d</sha1>
  </revision>
  <revision>
    <id>743</id>
    <parentid>742</parentid>
    <timestamp>2016-06-30T04:24:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4091" xml:space="preserve">__NOTOC__ __NOEDITSECTION__
&lt;div&gt;
[[File:Reachback-def-jp-3-30.png|framed|left]]
&lt;/div&gt;

=Situation Center=

{|
|style="vertical-align:top"|{{#viki:pageTitles=Current Activities, Surface Exposure|width=500|height=500}}
|}

=Progress Status=

{|-
| style="color:#000;padding:2px 3px 3px" | &lt;div&gt;
&lt;br /&gt;
  '''[[MediaWiki:Overarching|Overarching]]''' Guiding Instruments
  * Center of Gravity
  * '''[[Crown Jewels Analysis]]'''
  * Targeting Assessment Countering Analysis (TCAC)
  * '''[[Cyber Early Warning|Cyber Threats]]''' and '''[[ABI-INTRO|methodology]]'''
&lt;/div&gt;
|}

''' Complete '''
&lt;br /&gt;
* Deployment into the reachback.io as the primary family
 MOBOPS namespace included as family member
 MOBOPS namespace interlink translation to CIMACELL extended family
* Custom monitoring for information leaks (paste sites, TOR to clear dump links etc.)
* Passive sensor placements (DNS)
* Harvesting agent placements (Surface Exposure and Targeting)
* Established links to allow emerging associations and pattern analysis 

''' Ongoing '''
* Defining Centers of Gravity 
* Global Awareness - provide awareness of the current landscape.
* Threat  Analysis - a semantic based analytically living product.. 
* Surface Exposure - visually representation showing the surface exposure to pinpoint areas of interest and support in minimizing.
* Identifying domains, websites, and dns and other online assets with a direct relationship]
* Identifying third parties, trusted business partners, vendors, and others indirect relationships 
* Learning the people, personalities, and positions within the organization to assess their ability to help obtain access.
* Learning the technology and internal structure and staff responsible for the various areas the technology is used.
* Multi discipline intelligence activities
* Link analysis, historical timeline, and social network analysis using online social network media

=Risk Factors=

&lt;br /&gt;
The methodology used in risk and vulnerability analysis was developed to compliment the best practices found in fortune 50 organizations, and organizations like MITRE.  Our hybrid solution is unique both in the innovative use of technology and in our counter target centric approach.
&lt;br /&gt;
{{New Paragraph}}
&lt;big&gt;''' Third Parties '''&lt;/big&gt;
&lt;br /&gt;
Other organizations who deal with Motability data and therefore may pose a third party risk.
* httx://www.rsagroup.com/rsagroup/en/home Royal Sun Alliance Insurance
* httx://www.rac.co.uk/new The RAC
* httxs://www.kwik-fit.com/home.asp Kwik Fit
{{New Paragraph}}
&lt;big&gt;''' Computer Networks '''&lt;/big&gt;
&lt;br /&gt;
[[IPV4_info|MOBOPS Identified IP addresses]]
&lt;br /&gt;
[[Certificates|Digital Certificates]]
{{New Paragraph}}
&lt;big&gt;'''Open Source'''&lt;/big&gt;
*Associated domains - 30+ direct 10+ indirect - note this is not an effort to identify MOBOPS “owned assets” but rather MOBOPS “assets to protect” and the accepting risks resulting from outside or uncontrollable through normal risk management processes.  
*Associated email accounts - 30+ high value accounts that could be used as part of an attack plan. 
*Associated technologies - Video appears to be of interest but for purposes not directly obvious for use in attack.  Our team will continue to identify the interest and initially make attempts to determine any covert communications directly related to an attack and providing command and control (C2) functions and the possible manipulation by third parties for their benefit.     
*Social Media - we have started to look into the social media practices of MOBOPS for comparison with research datasets.  Our services are focused in sentiment analysis, influence, rumor analysis, and deception detection and deceptive countermeasures for protection.  If there are requirements or desires for social media monitoring or trend analysis we have an extensive list of providers and services ranging from free to geared for government pricing that can be accessed for assisting in such areas.

&lt;headertabs /&gt;

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>0ba8a67a7aaf8e1225a512e66770c781017bcfa1</sha1>
  </revision>
  <revision>
    <id>744</id>
    <parentid>743</parentid>
    <timestamp>2016-06-30T04:25:41Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3958" xml:space="preserve">__NOTOC__ __NOEDITSECTION__

=Overview=

[[File:Reachback-def-jp-3-30.png|framed|left]]


=Progress Status=

{|-
| style="color:#000;padding:2px 3px 3px" | &lt;div&gt;
&lt;br /&gt;
  '''[[MediaWiki:Overarching|Overarching]]''' Guiding Instruments
  * Center of Gravity
  * '''[[Crown Jewels Analysis]]'''
  * Targeting Assessment Countering Analysis (TCAC)
  * '''[[Cyber Early Warning|Cyber Threats]]''' and '''[[ABI-INTRO|methodology]]'''
&lt;/div&gt;
|}

''' Complete '''
&lt;br /&gt;
* Deployment into the reachback.io as the primary family
 MOBOPS namespace included as family member
 MOBOPS namespace interlink translation to CIMACELL extended family
* Custom monitoring for information leaks (paste sites, TOR to clear dump links etc.)
* Passive sensor placements (DNS)
* Harvesting agent placements (Surface Exposure and Targeting)
* Established links to allow emerging associations and pattern analysis 

''' Ongoing '''
* Defining Centers of Gravity 
* Global Awareness - provide awareness of the current landscape.
* Threat  Analysis - a semantic based analytically living product.. 
* Surface Exposure - visually representation showing the surface exposure to pinpoint areas of interest and support in minimizing.
* Identifying domains, websites, and dns and other online assets with a direct relationship]
* Identifying third parties, trusted business partners, vendors, and others indirect relationships 
* Learning the people, personalities, and positions within the organization to assess their ability to help obtain access.
* Learning the technology and internal structure and staff responsible for the various areas the technology is used.
* Multi discipline intelligence activities
* Link analysis, historical timeline, and social network analysis using online social network media

=Risk Factors=

&lt;br /&gt;
The methodology used in risk and vulnerability analysis was developed to compliment the best practices found in fortune 50 organizations, and organizations like MITRE.  Our hybrid solution is unique both in the innovative use of technology and in our counter target centric approach.
&lt;br /&gt;
{{New Paragraph}}
&lt;big&gt;''' Third Parties '''&lt;/big&gt;
&lt;br /&gt;
Other organizations who deal with Motability data and therefore may pose a third party risk.
* httx://www.rsagroup.com/rsagroup/en/home Royal Sun Alliance Insurance
* httx://www.rac.co.uk/new The RAC
* httxs://www.kwik-fit.com/home.asp Kwik Fit
{{New Paragraph}}
&lt;big&gt;''' Computer Networks '''&lt;/big&gt;
&lt;br /&gt;
[[IPV4_info|MOBOPS Identified IP addresses]]
&lt;br /&gt;
[[Certificates|Digital Certificates]]
{{New Paragraph}}
&lt;big&gt;'''Open Source'''&lt;/big&gt;
*Associated domains - 30+ direct 10+ indirect - note this is not an effort to identify MOBOPS “owned assets” but rather MOBOPS “assets to protect” and the accepting risks resulting from outside or uncontrollable through normal risk management processes.  
*Associated email accounts - 30+ high value accounts that could be used as part of an attack plan. 
*Associated technologies - Video appears to be of interest but for purposes not directly obvious for use in attack.  Our team will continue to identify the interest and initially make attempts to determine any covert communications directly related to an attack and providing command and control (C2) functions and the possible manipulation by third parties for their benefit.     
*Social Media - we have started to look into the social media practices of MOBOPS for comparison with research datasets.  Our services are focused in sentiment analysis, influence, rumor analysis, and deception detection and deceptive countermeasures for protection.  If there are requirements or desires for social media monitoring or trend analysis we have an extensive list of providers and services ranging from free to geared for government pricing that can be accessed for assisting in such areas.

&lt;headertabs /&gt;

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>c78900ec09fbb17901ff2f046bc733c3d0022857</sha1>
  </revision>
  <revision>
    <id>752</id>
    <parentid>744</parentid>
    <timestamp>2016-09-09T09:15:51Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Replaced content with "__NOTOC__ __NOEDITSECTION__  =Overview=  [[File:Reachback-def-jp-3-30.png|framed|left]]   {{#set:Name={{PAGENAME}}}}  {{DISPLAYTITLE: Reachback Operations}} {{#set:Title I..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="186" xml:space="preserve">__NOTOC__ __NOEDITSECTION__

=Overview=

[[File:Reachback-def-jp-3-30.png|framed|left]]


{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>1db63a094ecb4a2d078f5a4ba53b97d2580cad48</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>File:Gears.png</title>
  <ns>6</ns>
  <id>304</id>
  <revision>
    <id>735</id>
    <timestamp>2016-06-30T03:08:24Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>Protect</title>
  <ns>0</ns>
  <id>305</id>
  <revision>
    <id>736</id>
    <timestamp>2016-06-30T03:48:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Glossary Term |Glossary Definition=To cover or shield from exposure, damage, or destruction. To keep from harm, attack, injury or exploitation. To maintain the status or int..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="281" xml:space="preserve">{{Glossary Term
|Glossary Definition=To cover or shield from exposure, damage, or destruction. To keep from harm, attack, injury or exploitation. To maintain the status or integrity of. To take action to guard against espionage or capture of sensitive equipment and information.
}}</text>
    <sha1>5522a6241060d223a75e207ee308f7be8d18db84</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>PROTECT</title>
  <ns>0</ns>
  <id>306</id>
  <revision>
    <id>737</id>
    <timestamp>2016-06-30T03:49:29Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Glossary Term |Glossary Term=Protect |Glossary Definition=To cover or shield from exposure, damage, or destruction. To keep from harm, attack, injury or exploitation. To mai..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="304" xml:space="preserve">{{Glossary Term
|Glossary Term=Protect
|Glossary Definition=To cover or shield from exposure, damage, or destruction. To keep from harm, attack, injury or exploitation. To maintain the status or integrity of. To take action to guard against espionage or capture of sensitive equipment and information.
}}</text>
    <sha1>3683d9444078e0992b727c28e9f500b068a2d096</sha1>
  </revision>
  <revision>
    <id>738</id>
    <parentid>737</parentid>
    <timestamp>2016-06-30T03:50:00Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="307" xml:space="preserve">{{Glossary Term
|Glossary Term=Protect
|Glossary Definition=To cover or shield from exposure, damage, or destruction. 
To keep from harm, attack, injury or exploitation. 
To maintain the status or integrity of. 
To take action to guard against espionage or capture of sensitive equipment and information.
}}</text>
    <sha1>b649261ec28ac652f320543c28834a7b4b843ba2</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>File:Reachback-def-jp-3-30.png</title>
  <ns>6</ns>
  <id>307</id>
  <revision>
    <id>739</id>
    <timestamp>2016-06-30T04:21:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>Property:Hierarchy Data</title>
  <ns>102</ns>
  <id>47</id>
  <revision>
    <id>745</id>
    <parentid>71</parentid>
    <timestamp>2016-07-13T20:36:12Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="75" xml:space="preserve">This is a property of type [[Has type::Code]].
[[Category:Framework Pages]]</text>
    <sha1>07091ad5ce8600dd3cd56a1c65d7369ae3aaa5ea</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>Property:Hide Title Icon</title>
  <ns>102</ns>
  <id>308</id>
  <revision>
    <id>746</id>
    <timestamp>2016-07-13T20:40:31Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Text]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Text]].</text>
    <sha1>7a219f48fc26b2aae6b81b105b75d5cda6cb6a92</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>File:Characterizing-effects-cyber-adversary.pdf</title>
  <ns>6</ns>
  <id>309</id>
  <revision>
    <id>747</id>
    <timestamp>2016-07-21T00:07:20Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>748</id>
    <parentid>747</parentid>
    <timestamp>2016-07-21T00:07:48Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[File:Characterizing-effects-cyber-adversary-13-4173.pdf]] to [[File:Characterizing-effects-cyber-adversary.pdf]] without leaving a redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>749</id>
    <parentid>748</parentid>
    <timestamp>2016-07-21T00:08:22Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22" xml:space="preserve">[[Category:Resources]]</text>
    <sha1>8e670026d35cdefe0315772d2adb5392b9928605</sha1>
  </revision>
</page>
<page arvcontinue="20160507184616|703">
  <title>Property:Foaf:mbox</title>
  <ns>102</ns>
  <id>310</id>
  <revision>
    <id>750</id>
    <timestamp>2016-07-26T00:23:25Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created a property of type [[Has type::Page]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">This is a property of type [[Has type::Page]].</text>
    <sha1>a77920a9d24db1d24320cdd74718a3bf351bd0c9</sha1>
  </revision>
  <revision>
    <id>751</id>
    <parentid>750</parentid>
    <timestamp>2016-07-26T00:23:57Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="880" xml:space="preserve">This property represents the imported [[FOAF]] property. It is used to specify someones [[has type::email]] address in URI-form. However: '''Do not use ''foaf:mbox'' directly.''' Instead, use the template [[Template:mailbox]] as follows:

 &lt;nowiki&gt;{{mailbox|someone@somewhere.org}}&lt;/nowiki&gt;

to get multiple annotations in one step: one with ''foaf:mbox'' and one with [[Property:email]]. To still use ''foaf:mbox'', one would write

 &lt;nowiki&gt;[[foaf:mbox::mailto:someone@somewhere.org]]&lt;/nowiki&gt;

where "mailto:" is important.

'''Attention:''' FOAF specifies that everything with a value for ''foaf:mbox'' is a ''foaf:Agent'', i.e. some entity that can do something. So do not use ''foaf:mbox'' to assign an email, e.g., to a conference. An alternative to ''foaf:mbox'' is [[Property:email]] which encodes emails as a string (without "mailto:" and without a FOAF interpretation).</text>
    <sha1>4e7e2e9582bab0f53b6f586d78c0ff86b02421d1</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Knowledge Center</title>
  <ns>0</ns>
  <id>200</id>
  <revision>
    <id>753</id>
    <parentid>752</parentid>
    <timestamp>2016-09-09T09:16:21Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="172" xml:space="preserve">__NOTOC__ __NOEDITSECTION__
[[File:Reachback-def-jp-3-30.png|framed|left]]

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>aba6831669f86ba40416721eda9a73f04f9bf816</sha1>
  </revision>
  <revision>
    <id>756</id>
    <parentid>753</parentid>
    <timestamp>2016-10-06T19:37:31Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">__NOTOC__ __NOEDITSECTION__
[[File:World Banner.png|framed|left]]

{{#set:Name={{PAGENAME}}}} 
{{DISPLAYTITLE: Reachback Operations}}
{{#set:Title Icon=Gears.png}}</text>
    <sha1>360a2a5c01cc422a5a5c9c2f94a733f298e19846</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:COG.png</title>
  <ns>6</ns>
  <id>311</id>
  <revision>
    <id>754</id>
    <timestamp>2016-10-06T19:36:36Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:World Banner.png</title>
  <ns>6</ns>
  <id>312</id>
  <revision>
    <id>755</id>
    <timestamp>2016-10-06T19:36:59Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:Gears.png</title>
  <ns>6</ns>
  <id>304</id>
  <revision>
    <id>757</id>
    <parentid>735</parentid>
    <timestamp>2016-10-06T19:38:07Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie uploaded a new version of [[File:Gears.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>CIP FRAMEWORK</title>
  <ns>0</ns>
  <id>313</id>
  <revision>
    <id>758</id>
    <timestamp>2016-11-25T16:55:40Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The '''Corporate Intelligence Priorities Framework'' is a SENSITIVE document used by the top planners and decision makers within the organization.  This summarizes the organiz..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2370" xml:space="preserve">The '''Corporate Intelligence Priorities Framework'' is a SENSITIVE document used by the top planners and decision makers within the organization.  This summarizes the organizations information gathering  priorities.  

This document typically does not change although certain events such as merging with another organization or changes in law or locations operating can be reason for modify or rewrite.

'''The Warning Conundrum'''

Today’s dispersed, fast-changing threat environment, in which the capabilities of adversaries are increasingly enhanced by technological advances, challenges organizations as never before.   '''Warning''' is designed not only to avert intelligence failures; it also strives to prepare consumers to respond to unanticipated developments—indeed, to expect such developments in the years ahead.   Incorporating  '''strategic warning''' in the process to establish and define substantive priorities will assist in effectively managing resources to cover crises and standing requirements.

1.  An agile, accessible, and automated framework.  

Although all members agree that the Organization needs some type of prioritization scheme, they stress that it must not only be customer-derived, but also dynamic, accessible, and appropriate for the current digital collection, production, and resource management environment.

2.  A rational, coherent structure to support analysis, collection, and systems acquisition.  

Recognizing that the corporate-level priorities framework must support the current and future needs of the analytic and collection activities, the guidance must be both broad and  specific—ensuring the necessary granularity to drive the development of collection requirements management systems, as well as future systems acquisition.
 
3.  Integrating national priorities documents and strategic analysis.  To prepare for future intelligence challenges, the national-level priorities framework should integrate strategic estimates and analytic products into its calculations.   Combined with adding accountability to the “warning” and “risk management” procedures, these changes will minimize the chances of strategic surprise and intelligence failure.

4. Improving strategic warning.  Among other advances, we should apply greater analytic rigor and methodologically grounded approaches to our assessments.</text>
    <sha1>36ae24df0de951bf0784b6e6e54d4d98832f410d</sha1>
  </revision>
  <revision>
    <id>765</id>
    <parentid>758</parentid>
    <timestamp>2016-11-25T17:46:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[CIPF FRAMEWORK]] to [[CIP FRAMEWORK]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2370" xml:space="preserve">The '''Corporate Intelligence Priorities Framework'' is a SENSITIVE document used by the top planners and decision makers within the organization.  This summarizes the organizations information gathering  priorities.  

This document typically does not change although certain events such as merging with another organization or changes in law or locations operating can be reason for modify or rewrite.

'''The Warning Conundrum'''

Today’s dispersed, fast-changing threat environment, in which the capabilities of adversaries are increasingly enhanced by technological advances, challenges organizations as never before.   '''Warning''' is designed not only to avert intelligence failures; it also strives to prepare consumers to respond to unanticipated developments—indeed, to expect such developments in the years ahead.   Incorporating  '''strategic warning''' in the process to establish and define substantive priorities will assist in effectively managing resources to cover crises and standing requirements.

1.  An agile, accessible, and automated framework.  

Although all members agree that the Organization needs some type of prioritization scheme, they stress that it must not only be customer-derived, but also dynamic, accessible, and appropriate for the current digital collection, production, and resource management environment.

2.  A rational, coherent structure to support analysis, collection, and systems acquisition.  

Recognizing that the corporate-level priorities framework must support the current and future needs of the analytic and collection activities, the guidance must be both broad and  specific—ensuring the necessary granularity to drive the development of collection requirements management systems, as well as future systems acquisition.
 
3.  Integrating national priorities documents and strategic analysis.  To prepare for future intelligence challenges, the national-level priorities framework should integrate strategic estimates and analytic products into its calculations.   Combined with adding accountability to the “warning” and “risk management” procedures, these changes will minimize the chances of strategic surprise and intelligence failure.

4. Improving strategic warning.  Among other advances, we should apply greater analytic rigor and methodologically grounded approaches to our assessments.</text>
    <sha1>36ae24df0de951bf0784b6e6e54d4d98832f410d</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Intelligence Priorities</title>
  <ns>0</ns>
  <id>314</id>
  <revision>
    <id>759</id>
    <timestamp>2016-11-25T17:11:17Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "'''Goal'''  To foster development of coherent strategies to establish substantive priorities that meet the competing demands of policymakers and corporate leadership for curre..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="697" xml:space="preserve">'''Goal'''

To foster development of coherent strategies to establish substantive priorities that meet the competing demands of policymakers and corporate leadership for current intelligence, long-term analysis, and strategic warning, and to provide collectors with more specific requirements guidance.  The [[CIP FRAMEWOK]] provides an overall structure in developing overarching corporate priorities followed by decision makers, strategic analysis and early warning provisions.


Intelligence Priorities exist in hierarchies within the CIP Framework and must allow but also dynamic, accessible, and appropriate for the current digital collection, production, and resource management environment.</text>
    <sha1>64bbd017162129b3495108f12f8a8a6982cc0c2b</sha1>
  </revision>
  <revision>
    <id>760</id>
    <parentid>759</parentid>
    <timestamp>2016-11-25T17:11:39Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="698" xml:space="preserve">'''Goal'''

To foster development of coherent strategies to establish substantive priorities that meet the competing demands of policymakers and corporate leadership for current intelligence, long-term analysis, and strategic warning, and to provide collectors with more specific requirements guidance.  The [[CIP Framework]] provides an overall structure in developing overarching corporate priorities followed by decision makers, strategic analysis and early warning provisions.


Intelligence Priorities exist in hierarchies within the CIP Framework and must allow but also dynamic, accessible, and appropriate for the current digital collection, production, and resource management environment.</text>
    <sha1>ae6be6d86bc99cb31802121b83c33e0f93649eef</sha1>
  </revision>
  <revision>
    <id>761</id>
    <parentid>760</parentid>
    <timestamp>2016-11-25T17:12:39Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="699" xml:space="preserve">'''Goal'''

To foster development of coherent strategies to establish substantive priorities that meet the competing demands of policymakers and corporate leadership for current intelligence, long-term analysis, and strategic warning, and to provide collectors with more specific requirements guidance.  The [[CIPF FRAMEWORK]] provides an overall structure in developing overarching corporate priorities followed by decision makers, strategic analysis and early warning provisions.


Intelligence Priorities exist in hierarchies within the CIP Framework and must allow but also dynamic, accessible, and appropriate for the current digital collection, production, and resource management environment.</text>
    <sha1>aed14cc882bd12d406e68ba5c4a0e8fdb945832c</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>CRITICAL INTELLIGENCE</title>
  <ns>0</ns>
  <id>315</id>
  <revision>
    <id>762</id>
    <timestamp>2016-11-25T17:19:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Glossary Term |Glossary Term=Critical Intelligence |Glossary Definition=Intelligence that is crucial and requires the immediate attention of the commander. It is required to..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="714" xml:space="preserve">{{Glossary Term
|Glossary Term=Critical Intelligence
|Glossary Definition=Intelligence that is crucial and requires the immediate attention of the commander. It is required to enable the commander to make decisions that will provide a timely and appropriate response to actions by the potential or actual enemy. It includes but is not limited to the following: 1) strong indications of the imminent outbreak of hostilities of any type (warning of attack); 2) aggression of any nature against a friendly country; 3) indications or use of nuclear, biological, and chemical weapons; or 4) significant events within potential enemy countries that may lead to modification of nuclear strike plans. (JP 1-02 &amp; JP 2-0)
}}</text>
    <sha1>a19f7aee02e9baa914e133db8ca315cd38479215</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>CRITICAL INFORMATION</title>
  <ns>0</ns>
  <id>316</id>
  <revision>
    <id>763</id>
    <timestamp>2016-11-25T17:21:30Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Glossary Term |Glossary Term=Critical Information |Glossary Definition=Specific facts about friendly intentions, capabilities, and activities vitally needed by adversaries f..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="319" xml:space="preserve">{{Glossary Term
|Glossary Term=Critical Information
|Glossary Definition=Specific facts about friendly intentions, capabilities, and activities vitally needed by adversaries for them to plan and act effectively to guarantee failure or unacceptable consequences for friendly mission accomplishment. (JP 1-02 &amp; JP 2-0)
}}</text>
    <sha1>2b3baadc11e750f8af841d94f6572dc34d20ed21</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>COMMANDERS CRITICAL INFORMATION REQUIREMENT</title>
  <ns>0</ns>
  <id>317</id>
  <revision>
    <id>764</id>
    <timestamp>2016-11-25T17:27:46Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Glossary Term |Glossary Term=Commanders Critical Information Requirement |Glossary Definition=An information requirement identified by the commander as being critical to fac..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="335" xml:space="preserve">{{Glossary Term
|Glossary Term=Commanders Critical Information Requirement
|Glossary Definition=An information requirement identified by the commander as being critical to facilitating timely decision-making. The two key elements are friendly force information requirements and priority intelligence requirements. (JP 1-02 &amp; JP 3-0)
}}</text>
    <sha1>cd9bccf00c5bab9d336bdec05cd0a2d43cc34035</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>CIPF FRAMEWORK</title>
  <ns>0</ns>
  <id>318</id>
  <revision>
    <id>766</id>
    <timestamp>2016-11-25T17:46:53Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie moved page [[CIPF FRAMEWORK]] to [[CIP FRAMEWORK]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="27" xml:space="preserve">#REDIRECT [[CIP FRAMEWORK]]</text>
    <sha1>e0ed834bc7176c1c540aa57574030548d5b1ec24</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:Intel-process.png</title>
  <ns>6</ns>
  <id>319</id>
  <revision>
    <id>767</id>
    <timestamp>2016-11-25T18:42:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>The Intelligence Process</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24" xml:space="preserve">The Intelligence Process</text>
    <sha1>a6252fc0b95a0e2a1bc93dc5926deb361d7e85a0</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Intelligence Process Missing - Planning and Direction</title>
  <ns>0</ns>
  <id>320</id>
  <revision>
    <id>768</id>
    <timestamp>2016-11-25T18:45:03Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:Intel-process.png|frame|left|An image showing a typical example of the intelligence process]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="100" xml:space="preserve">[[File:Intel-process.png|frame|left|An image showing a typical example of the intelligence process]]</text>
    <sha1>97ad3e67e88f121baa0b9fe04b5a11d1dcc4d4a5</sha1>
  </revision>
  <revision>
    <id>769</id>
    <parentid>768</parentid>
    <timestamp>2016-11-25T18:45:55Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="104" xml:space="preserve">[[File:Intel-process.png|400|frame|left|An image showing a typical example of the intelligence process]]</text>
    <sha1>65c76bb41cb699e9a9b4067f050dc341969645d6</sha1>
  </revision>
  <revision>
    <id>770</id>
    <parentid>769</parentid>
    <timestamp>2016-11-25T19:23:17Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2514" xml:space="preserve">[[File:Intel-process.png|400|frame|left|An image showing a typical example of the intelligence process]]

Several examples can be found showing the intelligence process and may differ slightly to suit an audience.

Each of them begin the same in the cycle with the first state of '''Planning and Direction'''.

Military and intelligence organizations understand the significance it's placed within the cycle represented such as above.

While not true of all but very close to every corporate organization has no knowledge or experience working in the intelligence field.

The Information Security industry has increasingly changed their brand to include "threat intelligence" capabilities and services.
As well, the security industry marketing for intelligence lead security approaches is inherently impossible to do by the security industry.

An intelligence lead approach to Information Security is certainly an improved manner of operating, but would require experienced intelligence industry leading.
When this is not the case and intelligence professionals not helping other than use of their profession's books, guides and concepts.
When the CEO or another high level official is responsible for protection of the organization they will trust what their staff suggests or recommends, read about or hear from others.

The resulting services providing "threat intelligence" have often been purchased from most providers due to the vague descriptions or limited knowledge prior to subscribing.
 Such subscriptions are often sold as "feeds", and intelligence is definitely not a feed or information available to multiple consumers unless all of the information was based on developing an early warning system.  Research indicates most of these are information about a new form of malware or cyber activity located which can be very useful to know if the malware or activity would potentially have capabilities that would cause harm unless measures placed to prevent it.

Planning for these services aren't intelligence related and lack the perspective needed by those who are highly capable and focused on technical systems and networks and planning the new information and resource as it fits within their organization and operation.  An intelligence professional are also highly capable but focus on gaining and maintaining reach and the countermeasures to mislead or misdirect an investigation should one happen which would include attention is diverted from any source or asset to continue maintaining reach.</text>
    <sha1>1644006eabdaab1e3449288928668f81b8f818c7</sha1>
  </revision>
  <revision>
    <id>771</id>
    <parentid>770</parentid>
    <timestamp>2016-11-25T19:24:54Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2506" xml:space="preserve">[[File:Intel-process.png|400|frame|left|An image showing a typical example of the intelligence process]]

Several examples can be found showing the intelligence process and may differ slightly to suit an audience.

Each of them begin the same in the cycle with the first state of '''Planning and Direction'''.

Military and intelligence organizations understand the significance it's placed within the cycle represented such as above.

While not true of all but very close to every corporate organization has no knowledge or experience working in the intelligence field.

The Information Security industry has increasingly changed their brand to include "threat intelligence" capabilities and services.
As well, the security industry marketing for intelligence lead security approaches is inherently impossible to do by the security industry.

An intelligence lead approach to Information Security is certainly an improved manner of operating, but would require experienced intelligence industry leading.
When this is not the case and intelligence professionals not helping other than use of their profession's books, guides and concepts.


When the CEO or another high level official is responsible for protection of the organization they will trust suggestions, recommendations, read about or heard from others.

The resulting services providing "threat intelligence" have often been purchased from most providers due to the vague descriptions or limited knowledge prior to subscribing.
 Such subscriptions are often sold as "feeds", and intelligence is definitely not a feed or information available to multiple consumers unless all of the information was based on developing an early warning system.  Research indicates most of these are information about a new form of malware or cyber activity located which can be very useful to know if the malware or activity would potentially have capabilities that would cause harm unless measures placed to prevent it.

Planning for these services aren't intelligence related and lack the perspective needed by those who are highly capable and focused on technical systems and networks and planning the new information and resource as it fits within their organization and operation.  An intelligence professional are also highly capable but focus on gaining and maintaining reach and the countermeasures to mislead or misdirect an investigation should one happen which would include attention is diverted from any source or asset to continue maintaining reach.</text>
    <sha1>fbe4214ad018e9a6b9921a0f1b3ae2f6503598ef</sha1>
  </revision>
  <revision>
    <id>772</id>
    <parentid>771</parentid>
    <timestamp>2016-11-25T19:25:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2503" xml:space="preserve">[[File:Intel-process.png|400|frame|left|An image showing a typical example of the intelligence process]]

Several examples can be found showing the intelligence process and may differ slightly to suit an audience.

Each of them begin the same in the cycle with the first state of '''Planning and Direction'''.

Military and intelligence organizations understand the significance it's placed within the cycle represented such as above.

While not true of all but very close to every corporate organization has no knowledge or experience working in the intelligence field.

The Information Security industry has increasingly changed their brand to include "threat intelligence" capabilities and services.
As well, the security industry marketing for intelligence lead security approaches is inherently impossible to do by the security industry.

An intelligence lead approach to Information Security is certainly an improved manner of operating, but would require experienced intelligence industry leading.
When this is not the case and intelligence professionals not helping other than use of their profession's books, guides and concepts.


When the CEO or another high level official is responsible for protection of the organization they will trust suggestions, recommendations, read about or heard from others.The resulting services providing "threat intelligence" have often been purchased from most providers due to the vague descriptions or limited knowledge prior to subscribing. Such subscriptions are often sold as "feeds", and intelligence is definitely not a feed or information available to multiple consumers unless all of the information was based on developing an early warning system.  Research indicates most of these are information about a new form of malware or cyber activity located which can be very useful to know if the malware or activity would potentially have capabilities that would cause harm unless measures placed to prevent it.

Planning for these services aren't intelligence related and lack the perspective needed by those who are highly capable and focused on technical systems and networks and planning the new information and resource as it fits within their organization and operation.  An intelligence professional are also highly capable but focus on gaining and maintaining reach and the countermeasures to mislead or misdirect an investigation should one happen which would include attention is diverted from any source or asset to continue maintaining reach.</text>
    <sha1>f8bdb7984b6343e7ef049515d7d75d40b4dda86d</sha1>
  </revision>
  <revision>
    <id>773</id>
    <parentid>772</parentid>
    <timestamp>2016-11-25T19:28:20Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Eddie moved page [[Intelligence Process]] to [[Intelligence Process Missing - Planning and Direction]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2503" xml:space="preserve">[[File:Intel-process.png|400|frame|left|An image showing a typical example of the intelligence process]]

Several examples can be found showing the intelligence process and may differ slightly to suit an audience.

Each of them begin the same in the cycle with the first state of '''Planning and Direction'''.

Military and intelligence organizations understand the significance it's placed within the cycle represented such as above.

While not true of all but very close to every corporate organization has no knowledge or experience working in the intelligence field.

The Information Security industry has increasingly changed their brand to include "threat intelligence" capabilities and services.
As well, the security industry marketing for intelligence lead security approaches is inherently impossible to do by the security industry.

An intelligence lead approach to Information Security is certainly an improved manner of operating, but would require experienced intelligence industry leading.
When this is not the case and intelligence professionals not helping other than use of their profession's books, guides and concepts.


When the CEO or another high level official is responsible for protection of the organization they will trust suggestions, recommendations, read about or heard from others.The resulting services providing "threat intelligence" have often been purchased from most providers due to the vague descriptions or limited knowledge prior to subscribing. Such subscriptions are often sold as "feeds", and intelligence is definitely not a feed or information available to multiple consumers unless all of the information was based on developing an early warning system.  Research indicates most of these are information about a new form of malware or cyber activity located which can be very useful to know if the malware or activity would potentially have capabilities that would cause harm unless measures placed to prevent it.

Planning for these services aren't intelligence related and lack the perspective needed by those who are highly capable and focused on technical systems and networks and planning the new information and resource as it fits within their organization and operation.  An intelligence professional are also highly capable but focus on gaining and maintaining reach and the countermeasures to mislead or misdirect an investigation should one happen which would include attention is diverted from any source or asset to continue maintaining reach.</text>
    <sha1>f8bdb7984b6343e7ef049515d7d75d40b4dda86d</sha1>
  </revision>
  <revision>
    <id>775</id>
    <parentid>773</parentid>
    <timestamp>2016-11-25T19:38:02Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3086" xml:space="preserve">[[File:Intel-process.png|400|frame|left|An image showing a typical example of the intelligence process]]

Several examples can be found showing the intelligence process and may differ slightly to suit an audience.

Each of them begin the same in the cycle with the first state of '''Planning and Direction'''.

Military and intelligence organizations understand the significance it's placed within the cycle represented such as above.

While not true of all but very close to every corporate organization has no knowledge or experience working in the intelligence field.

'''On 'threat intelligence' from info-sec industry'''

Information Security as an industry has caused a significant amount of damage in their rebranding to include Intelligence in capability.  While increasing their sales and client lists the marketing campaign most often based on fear has caused far less noticed but much more extensive harm towards those who have or are familiar with working in the field of Intelligence and the difficult problem should their effort include implementing an intelligence lead approach to security.   

The Information Security industry has increasingly changed their brand to include "threat intelligence" capabilities and services.
As well, the security industry marketing for intelligence lead security approaches is inherently impossible to do by the security industry.
An intelligence lead approach to Information Security is certainly an improved manner of operating, but would require experienced intelligence industry leading.
When this is not the case and intelligence professionals not helping other than use of their profession's books, guides and concepts.

When the CEO or another high level official is responsible for protection of the organization they will trust suggestions, recommendations, read about or heard from others.The resulting services providing "threat intelligence" have often been purchased from most providers due to the vague descriptions or limited knowledge prior to subscribing. Such subscriptions are often sold as "feeds", and intelligence is definitely not a feed or information available to multiple consumers unless all of the information was based on developing an early warning system.  Research indicates most of these are information about a new form of malware or cyber activity located which can be very useful to know if the malware or activity would potentially have capabilities that would cause harm unless measures placed to prevent it.

Planning for these services aren't intelligence related and lack the perspective needed by those who are highly capable and focused on technical systems and networks and planning the new information and resource as it fits within their organization and operation.  An intelligence professional are also highly capable but focus on gaining and maintaining reach and the countermeasures to mislead or misdirect an investigation should one happen which would include attention is diverted from any source or asset to continue maintaining reach.

[[Planning and Direction]]  [[Intelligence]]</text>
    <sha1>93faf7aa0e5e67e7155fa32607adcba2b762da0d</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Intelligence Process</title>
  <ns>0</ns>
  <id>321</id>
  <revision>
    <id>774</id>
    <timestamp>2016-11-25T19:28:20Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Eddie moved page [[Intelligence Process]] to [[Intelligence Process Missing - Planning and Direction]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="67" xml:space="preserve">#REDIRECT [[Intelligence Process Missing - Planning and Direction]]</text>
    <sha1>cfe9d5bc8df90ab6753d5070dfb9ea25a3efd374</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Template:Field Manual</title>
  <ns>10</ns>
  <id>189</id>
  <revision>
    <id>776</id>
    <parentid>433</parentid>
    <timestamp>2016-11-25T19:49:26Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="228" xml:space="preserve">&lt;noinclude&gt;
This is the "Field Manual" template.
It should be called in the following format:
&lt;pre&gt;
{{Field Manual
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
|}
&lt;/includeonly&gt;</text>
    <sha1>ad4621fd4cc64f7be2f2062c80c5eb606fd9d2d6</sha1>
  </revision>
  <revision>
    <id>777</id>
    <parentid>776</parentid>
    <timestamp>2016-11-25T19:49:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1291" xml:space="preserve">&lt;includeonly&gt;

[[Category:Field Manual]]

= Description =
{| style="width: 25em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: both; text-align:left; "
! style="text-align: center; background-color:#ccccff;" colspan="2" |&lt;big&gt;{{PAGENAME}} [ [[Special:EditData/Field Manual/{{PAGENAME}}|Edit]] ]&lt;/big&gt;
|-
!style="vertical-align:top;"|Front Cover:
| [[Image::{{{img|}}}|]] [[Image:{{{img|}}}|100px]]
|-
!FM:
| [[FM::{{{fm}}}]]
|-
!Title:
| {{ #if: {{{title}}} | [[Title::{{{title|}}}]] | }}
|-
!Series:
| {{ #if: {{{series}}} | [[Series::{{{series|}}}]] | }}
|-
!Publication Date:
| {{ #if: {{{pubdate}}} | [[publication date::{{{pubdate|}}}]] | }}
|-
!PDF download:
| {{ #if: {{{url}}} | [[URL::{{{url|}}}]] | }}
|-
!ePub download:
| {{ #if: {{{epub}}} | [[epub::{{{epub|}}}|.epub]] | }}
|-
!Kindle download:
| {{ #if: {{{kindle}}} | [[kindle::{{{kindle|}}}|.mobi]] | }}
|-
|}''
{{{description|}}}

= Cited by pages =

{{ #ask: [[Main:+]] ([[Doctrine::{{PAGENAME}}]] OR [[Source::{{PAGENAME}}]] OR [[references::{{PAGENAME}}]])
| format=table
}}

= Image Gallery =

{{ #ask: [[Image:+]] [[Source::{{PAGENAME}}]]
| format=list
}}

&lt;headertabs/&gt;

__NOEDITSECTION__
&lt;/includeonly&gt;</text>
    <sha1>a3dcd3fa11ae3b6abfc4c79931ea96dd60c14dfe</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Form:Field Manual</title>
  <ns>106</ns>
  <id>322</id>
  <revision>
    <id>778</id>
    <timestamp>2016-11-25T19:50:17Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Field Manual" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1032" xml:space="preserve">&lt;noinclude&gt;
This is the "Field Manual" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=Field Manual}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Field Manual}}}
{| class="formtable"
! Fm: 
| {{{field|fm}}}
|-
! Description: 
| {{{field|description}}}
|-
! Img: 
| {{{field|img}}}
|-
! Title: 
| {{{field|title}}}
|-
! Series: 
| {{{field|series}}}
|-
! Pubdate: 
| {{{field|pubdate}}}
|-
! Url: 
| {{{field|url}}}
|-
! Epub: 
| {{{field|epub}}}
|-
! Kindle: 
| {{{field|kindle}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>437c31e83809c3eb7cc55fa0f442ba90632cda1f</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>FM 3-38</title>
  <ns>0</ns>
  <id>323</id>
  <revision>
    <id>779</id>
    <timestamp>2016-11-25T19:52:20Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "{{Field Manual |fm=FM 3-38 |title=CYBER ELECTRONIC ACTIVITIES |pubdate=FEB 2014 }}"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="82" xml:space="preserve">{{Field Manual
|fm=FM 3-38
|title=CYBER ELECTRONIC ACTIVITIES
|pubdate=FEB 2014
}}</text>
    <sha1>b18dd8a0a17082d059ec247603869449bc7e1864</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:FM-3-38.png</title>
  <ns>6</ns>
  <id>324</id>
  <revision>
    <id>780</id>
    <timestamp>2016-11-25T19:54:50Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>{{Image
|caption=Cyber Electromagnetic Activities
|source=File:FM-3-38.png
}}</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">{{Image
|caption=Cyber Electromagnetic Activities
|source=File:FM-3-38.png
}}</text>
    <sha1>9589d930103928385450cdf3203212e75aa4778e</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Template:Image</title>
  <ns>10</ns>
  <id>325</id>
  <revision>
    <id>781</id>
    <timestamp>2016-11-25T19:56:08Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;includeonly&gt;[[Caption::{{{caption}}}]]Source: [[Source::{{{source}}}]][[Upload Date::{{ #time: Y-m-d h:i:s | {{CURRENTTIMESTAMP}} }}| ]][[Category:Image]]&lt;/includeonly&gt;"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="169" xml:space="preserve">&lt;includeonly&gt;[[Caption::{{{caption}}}]]Source: [[Source::{{{source}}}]][[Upload Date::{{ #time: Y-m-d h:i:s | {{CURRENTTIMESTAMP}} }}| ]][[Category:Image]]&lt;/includeonly&gt;</text>
    <sha1>b76d33841fcdfdbd577350b61da7768707e2f43e</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:Rel-intel-info.png</title>
  <ns>6</ns>
  <id>326</id>
  <revision>
    <id>782</id>
    <timestamp>2016-11-25T20:21:35Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="72" xml:space="preserve">Relationships between Information Requirements and Intelligence Requests</text>
    <sha1>a43f29183d72a72b077fde95b0fa9dcd86c28b9f</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Planning and Direction</title>
  <ns>0</ns>
  <id>327</id>
  <revision>
    <id>783</id>
    <timestamp>2016-11-25T20:21:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Planning and Direction. IP and direction is best understood as the development of intelligence plans and the continuous management of their execution. Planning and direction a..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5565" xml:space="preserve">Planning and Direction. IP and direction is best understood as the development of
intelligence plans and the continuous management of their execution. Planning and direction
activities include, but are not limited to: the identification and prioritization of intelligence
requirements; the development of concepts of intelligence operations and architectures
required to support the commander’s mission; tasking subordinate intelligence elements for
the collection of information or the production of finished intelligence; submitting requests
for additional capabilities to higher headquarters; and submitting requests for collection,
exploitation, or all-source production support to external, supporting intelligence entities. IP
and direction occurs continuously as the intelligence component of the command’s campaign
and contingency adaptive planning effort. IP for campaign plans allows for the prioritization
of intelligence support across all ongoing operations and simultaneous planning efforts. On
the other hand, IP for contingency plans informs the development of joint capabilities and
enhances the readiness to respond to potential crises. The most likely threat scenarios are
used as the core of the deliberate planning effort for potential contingency operations. 

Through this effort, intelligence planners determine the personnel, equipment, and
intelligence architecture essential for support to joint operations. When a particular crisis
unfolds, commanders and their staffs develop an operation order (OPORD). Intelligence
input to the OPORD includes an adjusted and updated threat scenario and an intelligence
annex that tailors intelligence support to the nature and scope of operations to be conducted.
Assessments conducted by intelligence personnel provide operation planners feedback for
future planning for subsequent operations.
Intelligence support to joint operation planning is discussed in greater detail in Chapter IV,
“Intelligence Support to Planning, Executing, and Assessing Joint Operations.”
(1) Intelligence Requirement and Information Requirement Planning. During
mission analysis, the joint force staff identifies significant information gaps about the
adversary and other relevant aspects of the OE. After gap analysis, the staff formulates
intelligence requirements, which are general or specific subjects upon which there is a need
for the collection of information or the production of intelligence. All staff sections may
recommend intelligence requirements for designation as priority intelligence requirements 

(PIRs). However, the J-2 has overall staff responsibility for consolidating intelligence
requirement nominations from the staff and for making the overall recommendation to the
commander regarding their approval and their relative order of priority. Intelligence
requirements designated as PIRs receive increased levels of intelligence support and priority
in the allocation of intelligence resources while those not designated as PIR are satisfied as
time and resources allow. Ultimately, the commander designates PIRs, which together with
friendly force information requirements (FFIRs), constitute the commander’s critical
information requirements (CCIRs). Based on identified intelligence requirements (to include
PIRs), the staff develops a series of more specific questions known as information
requirements—those items of information that must be collected and processed to develop
the intelligence required by the commander. A subset of information requirements that are
related to and would answer a PIR are known as essential elements of information
(EEIs)—the most critical information requirements regarding the adversary and the OE
needed by the commander to assist in reaching a decision. The development of information
requirements (to include EEIs) leads to the generation of requests for information (RFIs). If
the required information is already available, a production requirement may be initiated, and
if the required information is not available, a collection requirement is initiated. Figure I-4
illustrates this process.
(a) The JFC uses PIRs as a tool to designate intelligence that is critical to
decision making, and to focus the intelligence system and the allocation of available
intelligence capabilities. PIR nominations consider the mission, commander’s intent,
operational objectives, and the time frame of expected operations. The JFC develops PIRs
that support critical decisions over the course of an operation, and for complex phased
operations, develops separate PIRs for each phase. As an operation ensues, the commander
updates PIRs to address new requirements or concerns, and as the situation changes, either
eliminates some or develops others. A JFC’s total number of PIRs for any phase of an
operation should reflect a reasonable balance between mission critical requirements and
finite intelligence support capability. Because of this, PIRs should be ranked and
disseminated in priority of importance. Other valid intelligence requirements are submitted,
but receive lower levels of intelligence support.
(b) Using PIRs as the basis, the intelligence staff develops the command’s
EEIs. To satisfy information requirements (to include EEIs), intelligence staffs should
identify the specific indicators that could fill a gap in the command’s knowledge and
understanding of adversary activities and other relevant aspects of the OE

[[File:Rel-intel-info.png|thumb|Relationship Between Intelligence Requirements and Information Requests]]</text>
    <sha1>d48a9ab999877ecb9f55982bdaab3c7660c5fa6c</sha1>
  </revision>
  <revision>
    <id>784</id>
    <parentid>783</parentid>
    <timestamp>2016-11-25T20:22:32Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5568" xml:space="preserve">Planning and Direction. IP and direction is best understood as the development of
intelligence plans and the continuous management of their execution. Planning and direction
activities include, but are not limited to: the identification and prioritization of intelligence
requirements; the development of concepts of intelligence operations and architectures
required to support the commander’s mission; tasking subordinate intelligence elements for
the collection of information or the production of finished intelligence; submitting requests
for additional capabilities to higher headquarters; and submitting requests for collection,
exploitation, or all-source production support to external, supporting intelligence entities. IP
and direction occurs continuously as the intelligence component of the command’s campaign
and contingency adaptive planning effort. IP for campaign plans allows for the prioritization
of intelligence support across all ongoing operations and simultaneous planning efforts. On
the other hand, IP for contingency plans informs the development of joint capabilities and
enhances the readiness to respond to potential crises. The most likely threat scenarios are
used as the core of the deliberate planning effort for potential contingency operations. 

Through this effort, intelligence planners determine the personnel, equipment, and
intelligence architecture essential for support to joint operations. When a particular crisis
unfolds, commanders and their staffs develop an operation order (OPORD). Intelligence
input to the OPORD includes an adjusted and updated threat scenario and an intelligence
annex that tailors intelligence support to the nature and scope of operations to be conducted.
Assessments conducted by intelligence personnel provide operation planners feedback for
future planning for subsequent operations.
Intelligence support to joint operation planning is discussed in greater detail in Chapter IV,
“Intelligence Support to Planning, Executing, and Assessing Joint Operations.”
(1) Intelligence Requirement and Information Requirement Planning. During
mission analysis, the joint force staff identifies significant information gaps about the
adversary and other relevant aspects of the OE. After gap analysis, the staff formulates
intelligence requirements, which are general or specific subjects upon which there is a need
for the collection of information or the production of intelligence. All staff sections may
recommend intelligence requirements for designation as priority intelligence requirements 

(PIRs). However, the J-2 has overall staff responsibility for consolidating intelligence
requirement nominations from the staff and for making the overall recommendation to the
commander regarding their approval and their relative order of priority. Intelligence
requirements designated as PIRs receive increased levels of intelligence support and priority
in the allocation of intelligence resources while those not designated as PIR are satisfied as
time and resources allow. Ultimately, the commander designates PIRs, which together with
friendly force information requirements (FFIRs), constitute the commander’s critical
information requirements (CCIRs). Based on identified intelligence requirements (to include
PIRs), the staff develops a series of more specific questions known as information
requirements—those items of information that must be collected and processed to develop
the intelligence required by the commander. A subset of information requirements that are
related to and would answer a PIR are known as essential elements of information
(EEIs)—the most critical information requirements regarding the adversary and the OE
needed by the commander to assist in reaching a decision. The development of information
requirements (to include EEIs) leads to the generation of requests for information (RFIs). If
the required information is already available, a production requirement may be initiated, and
if the required information is not available, a collection requirement is initiated. Figure I-4
illustrates this process.
(a) The JFC uses PIRs as a tool to designate intelligence that is critical to
decision making, and to focus the intelligence system and the allocation of available
intelligence capabilities. PIR nominations consider the mission, commander’s intent,
operational objectives, and the time frame of expected operations. The JFC develops PIRs
that support critical decisions over the course of an operation, and for complex phased
operations, develops separate PIRs for each phase. As an operation ensues, the commander
updates PIRs to address new requirements or concerns, and as the situation changes, either
eliminates some or develops others. A JFC’s total number of PIRs for any phase of an
operation should reflect a reasonable balance between mission critical requirements and
finite intelligence support capability. Because of this, PIRs should be ranked and
disseminated in priority of importance. Other valid intelligence requirements are submitted,
but receive lower levels of intelligence support.
(b) Using PIRs as the basis, the intelligence staff develops the command’s
EEIs. To satisfy information requirements (to include EEIs), intelligence staffs should
identify the specific indicators that could fill a gap in the command’s knowledge and
understanding of adversary activities and other relevant aspects of the OE

[[File:Rel-intel-info.png|left|Relationship Between Intelligence Requirements and Information Requirements]]</text>
    <sha1>3735c5efae409c88bb686274c27c1287e71164c8</sha1>
  </revision>
  <revision>
    <id>787</id>
    <parentid>784</parentid>
    <timestamp>2016-11-25T20:29:46Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8964" xml:space="preserve">Planning and Direction. IP and direction is best understood as the development of
intelligence plans and the continuous management of their execution. Planning and direction
activities include, but are not limited to: the identification and prioritization of intelligence
requirements; the development of concepts of intelligence operations and architectures
required to support the commander’s mission; tasking subordinate intelligence elements for
the collection of information or the production of finished intelligence; submitting requests
for additional capabilities to higher headquarters; and submitting requests for collection,
exploitation, or all-source production support to external, supporting intelligence entities. IP
and direction occurs continuously as the intelligence component of the command’s campaign
and contingency adaptive planning effort. IP for campaign plans allows for the prioritization
of intelligence support across all ongoing operations and simultaneous planning efforts. On
the other hand, IP for contingency plans informs the development of joint capabilities and
enhances the readiness to respond to potential crises. The most likely threat scenarios are
used as the core of the deliberate planning effort for potential contingency operations. 

Through this effort, intelligence planners determine the personnel, equipment, and
intelligence architecture essential for support to joint operations. When a particular crisis
unfolds, commanders and their staffs develop an operation order (OPORD). Intelligence
input to the OPORD includes an adjusted and updated threat scenario and an intelligence
annex that tailors intelligence support to the nature and scope of operations to be conducted.
Assessments conducted by intelligence personnel provide operation planners feedback for
future planning for subsequent operations.
Intelligence support to joint operation planning is discussed in greater detail in Chapter IV,
“Intelligence Support to Planning, Executing, and Assessing Joint Operations.”
(1) Intelligence Requirement and Information Requirement Planning. During
mission analysis, the joint force staff identifies significant information gaps about the
adversary and other relevant aspects of the OE. After gap analysis, the staff formulates
intelligence requirements, which are general or specific subjects upon which there is a need
for the collection of information or the production of intelligence. All staff sections may
recommend intelligence requirements for designation as priority intelligence requirements 

(PIRs). However, the J-2 has overall staff responsibility for consolidating intelligence
requirement nominations from the staff and for making the overall recommendation to the
commander regarding their approval and their relative order of priority. Intelligence
requirements designated as PIRs receive increased levels of intelligence support and priority
in the allocation of intelligence resources while those not designated as PIR are satisfied as
time and resources allow. Ultimately, the commander designates PIRs, which together with
friendly force information requirements (FFIRs), constitute the commander’s critical
information requirements (CCIRs). Based on identified intelligence requirements (to include
PIRs), the staff develops a series of more specific questions known as information
requirements—those items of information that must be collected and processed to develop
the intelligence required by the commander. A subset of information requirements that are
related to and would answer a PIR are known as essential elements of information
(EEIs)—the most critical information requirements regarding the adversary and the OE
needed by the commander to assist in reaching a decision. The development of information
requirements (to include EEIs) leads to the generation of requests for information (RFIs). If
the required information is already available, a production requirement may be initiated, and
if the required information is not available, a collection requirement is initiated. Figure I-4
illustrates this process.
(a) The JFC uses PIRs as a tool to designate intelligence that is critical to
decision making, and to focus the intelligence system and the allocation of available
intelligence capabilities. PIR nominations consider the mission, commander’s intent,
operational objectives, and the time frame of expected operations. The JFC develops PIRs
that support critical decisions over the course of an operation, and for complex phased
operations, develops separate PIRs for each phase. As an operation ensues, the commander
updates PIRs to address new requirements or concerns, and as the situation changes, either
eliminates some or develops others. A JFC’s total number of PIRs for any phase of an
operation should reflect a reasonable balance between mission critical requirements and
finite intelligence support capability. Because of this, PIRs should be ranked and
disseminated in priority of importance. Other valid intelligence requirements are submitted,
but receive lower levels of intelligence support.
(b) Using PIRs as the basis, the intelligence staff develops the command’s
EEIs. To satisfy information requirements (to include EEIs), intelligence staffs should
identify the specific indicators that could fill a gap in the command’s knowledge and
understanding of adversary activities and other relevant aspects of the OE

[[File:Rel-intel-info.png|left|Relationship Between Intelligence Requirements and Information Requirements]]

(c) In addition to joint forces intelligence requirements, the intelligence staff
must be aware of the intelligence requirements of higher, adjacent, subordinate, and

[[File:Intel-eii.png|thumb|Intelligence Essential Elements of Information]]

supported elements, the operational requirements of supported elements, as well as
national-level intelligence requirements.
(d) Subordinate units expand on the joint forces intelligence requirements by
making them specific enough to support their portion of the overall operation or campaign
and also develop intelligence requirements based on their own operational requirements.
The JFC’s PIRs should encompass and prioritize the most urgent intelligence requirements
of subordinate and supporting elements. Subordinate force intelligence requirements are
addressed and prioritized during planning. Conflicts for resources must be resolved and
unnecessary redundancies eliminated.
(e) PIRs assist the J-2 in determining and prioritizing the type and level of
intelligence resources required to support the joint force. Intelligence staffs use intelligence
requirements as a basis for: formulating statements of intelligence interest to the intelligence
community (IC); justifying tasking of national collection resources through the Defense
Intelligence Agency (DIA); and justifying requests for intelligence capabilities.
(f) Intelligence personnel review existing intelligence databases for potential
solutions to intelligence and information requirements. If the intelligence does not already
exist, the requestor issues an RFI—a specific time-sensitive ad hoc requirement for
information or intelligence products, distinct from standing requirements or scheduled
intelligence production. An RFI can be initiated at any level of command, and is validated in
accordance with the combatant command’s (CCMD’s) procedures. An RFI leads to a
production requirement, if the request can be answered with information on hand, or a
collection requirement, if the request requires collection of new information. Anticipated
production requirements are typically articulated in the form of analytic tasks and subtasks 

[[File:Key-term-specific-request.png|thumb]]

during planning and entered into the appropriate RFI management system during execution.
On the other hand, if an RFI leads to the initiation of a collection requirement, requestors of
intelligence collection support should provide specific information requirements (SIRs) to
allow the formulation of collection requirements and the allocation collection capabilities to
satisfy them. If the requestor does not provide SIRs, the collection manager should consult
with the requestor to determine the indicators of activity against which to focus collection
capabilities so that appropriate SIRs can be developed.

(g) To the extent possible, identify PIRs, EEIs, associated analytic tasks, and
SIRs in advance for each operational phase to provide the basis for synchronizing the
reception and integration of required intelligence capabilities. Collection capability
shortfalls identified during planning may form the basis for requests for forces (RFFs) and
requests for support from national intelligence resources. This information ensures that the
employment of defense intelligence capabilities is prioritized on supporting commanders in
achieving their operational objectives.</text>
    <sha1>078bdf52122fe716247b852bd15f54b4787eb5af</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:Intel-eii.png</title>
  <ns>6</ns>
  <id>328</id>
  <revision>
    <id>785</id>
    <timestamp>2016-11-25T20:26:20Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">Intelligence Essential Elements of Information</text>
    <sha1>5aa2aed335f17149f535da432205fa57b61b54e6</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:Key-term-specific-request.png</title>
  <ns>6</ns>
  <id>329</id>
  <revision>
    <id>786</id>
    <timestamp>2016-11-25T20:29:01Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42" xml:space="preserve">Key Term - Specific Collection Requirement</text>
    <sha1>fe7ab50f1fc389f088ae23e63a27c226b35fdd3f</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:Industry-best-practices.jpg</title>
  <ns>6</ns>
  <id>330</id>
  <revision>
    <id>788</id>
    <timestamp>2016-11-25T21:53:37Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:Call.jpg</title>
  <ns>6</ns>
  <id>331</id>
  <revision>
    <id>789</id>
    <timestamp>2016-11-25T21:59:01Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:Sylenth.jpg</title>
  <ns>6</ns>
  <id>332</id>
  <revision>
    <id>790</id>
    <timestamp>2016-11-25T22:07:49Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>File:120Sylenth.jpg</title>
  <ns>6</ns>
  <id>333</id>
  <revision>
    <id>791</id>
    <timestamp>2016-11-25T22:08:44Z</timestamp>
    <contributor>
      <username>Eddie</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>User:LibbyCarvosso82</title>
  <ns>2</ns>
  <id>334</id>
  <revision>
    <id>792</id>
    <timestamp>2020-03-13T15:38:27Z</timestamp>
    <contributor>
      <username>LibbyCarvosso82</username>
      <id>4</id>
    </contributor>
    <comment>Created page with "Hi, everybody! My name is Libby. &lt;br&gt;It is a little about myself: I live in Italy, my city of Prato Sesia. &lt;br&gt;It's called often Northern or cultural capital of NO. I've marri..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="340" xml:space="preserve">Hi, everybody! My name is Libby. &lt;br&gt;It is a little about myself: I live in Italy, my city of Prato Sesia. &lt;br&gt;It's called often Northern or cultural capital of NO. I've married 2 years ago.&lt;br&gt;I have 2 children - a son (Bonita) and the daughter (Lori). We all like Kayaking.&lt;br&gt;&lt;br&gt;my homepage; [https://Ello.co/uspsmahelizo usps liteblue]</text>
    <sha1>c6e37b4173a283569647d9f454ec07f0f53398a8</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>IO ROADMAP</title>
  <ns>0</ns>
  <id>335</id>
  <revision>
    <id>793</id>
    <timestamp>2022-03-18T14:00:43Z</timestamp>
    <contributor>
      <username>Tophatter</username>
      <id>5</id>
    </contributor>
    <comment>Created page with "INFORMATION OPERATIONS ROADMAP"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="30" xml:space="preserve">INFORMATION OPERATIONS ROADMAP</text>
    <sha1>f9637f6d2e9a0fb91ce51cfd534a7e69fa1bdb12</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Template:Forum</title>
  <ns>10</ns>
  <id>336</id>
  <revision>
    <id>794</id>
    <timestamp>2022-05-07T01:38:04Z</timestamp>
    <contributor>
      <username>Tophatter</username>
      <id>5</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Forum" template. It should be called in the following format: &lt;pre&gt; {{Forum |Name= |Description= |Link= |Interests= |Alignment= |Notes= }} &lt;/pre&gt; Edit..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="567" xml:space="preserve">&lt;noinclude&gt;
This is the "Forum" template.
It should be called in the following format:
&lt;pre&gt;
{{Forum
|Name=
|Description=
|Link=
|Interests=
|Alignment=
|Notes=
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
! Name
| [[Name::{{{Name|}}}]] 
|-
! Description
| [[Has description::{{{Description|}}}]] 
|-
! Link
| {{{Link|}}}
|-
! Interests
| [[Has interest::{{{Interests|}}}]] 
|-
! Associations
| [[Aligns with::{{{Alignment|}}}]] 
|-
! Notes
| [[Abstract::{{{Notes|}}}]] 
|}

[[Category:Online Forums]]
&lt;/includeonly&gt;</text>
    <sha1>25fbaaebaf1ea3bc448568bc7c6f8dfc9b1ba148</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Form:Forum</title>
  <ns>106</ns>
  <id>337</id>
  <revision>
    <id>795</id>
    <timestamp>2022-05-07T01:42:29Z</timestamp>
    <contributor>
      <username>Tophatter</username>
      <id>5</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Forum" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit t..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="698" xml:space="preserve">&lt;noinclude&gt;
This is the "Forum" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=Forum}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
==Community==
{{{section|Community|level=2|hidden}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>52b0ca7595793b423cb74171e2da7d6d19dd407c</sha1>
  </revision>
  <revision>
    <id>796</id>
    <parentid>795</parentid>
    <timestamp>2022-05-07T01:46:12Z</timestamp>
    <contributor>
      <username>Tophatter</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="961" xml:space="preserve">&lt;noinclude&gt;
This is the "Forum" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=Forum}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Forum}}}
{| class="formtable"
! Name: 
| {{{field|Name|mandatory|property=forumName}}}
|-
! Description: 
| {{{field|Description}}}
|-
! Link: 
| {{{field|Link}}}
|-
! Interests: 
| {{{field|Interests}}}
|-
! Alignment: 
| {{{field|Alignment}}}
|-
! Notes: 
| {{{field|Notes}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}


{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>9385930e49198eb2d4f26db964e449197af8817b</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Category:Online Forums</title>
  <ns>14</ns>
  <id>338</id>
  <revision>
    <id>797</id>
    <timestamp>2022-05-07T01:54:12Z</timestamp>
    <contributor>
      <username>Tophatter</username>
      <id>5</id>
    </contributor>
    <comment>Created page with "{{#default_form:Forum}}"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23" xml:space="preserve">{{#default_form:Forum}}</text>
    <sha1>d03729c5afafaf23ec1f3f99176204cd217899fe</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Template:Forum Member</title>
  <ns>10</ns>
  <id>339</id>
  <revision>
    <id>798</id>
    <timestamp>2022-05-07T02:05:01Z</timestamp>
    <contributor>
      <username>Tophatter</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="673" xml:space="preserve">&lt;noinclude&gt;
This is the "Forum Member" template.
It should be called in the following format:
&lt;pre&gt;
{{Forum Member
|Name=
|ID=
|Link=
|Avatar=
|Rank=
|Status=
|Contact=
|Membership=
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
! Name
| [[UserName::{{{Name|}}}]] 
|-
! ID
| [[ID::{{{ID|}}}]] 
|-
! Link
| [[Link::{{{Link|}}}]] 
|-
! Avatar
| [[Avatar::{{{Avatar|}}}]] 
|-
! Rank
| {{#arraymap:{{{Rank|}}}|,|x|[[Rank::x]]}}
|-
! Status
| {{#arraymap:{{{Status|}}}|,|x|[[Status::x]]}}
|-
! Contact
| [[Contact::{{{Contact|}}}]] 
|-
! Membership
| [[memberOf::{{{Membership|}}}]] 
|}

[[Category:Forum Members]]
&lt;/includeonly&gt;</text>
    <sha1>9a172a3526a7bf3d45cba41eab0bbc2d91b1c2b8</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Template:Advisory</title>
  <ns>10</ns>
  <id>340</id>
  <revision>
    <id>799</id>
    <timestamp>2022-05-11T08:49:22Z</timestamp>
    <contributor>
      <username>Tophatter</username>
      <id>5</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Advisory" template. It should be called in the following format: &lt;pre&gt; {{Advisory |ID= |Handling= |Title= |AdvisorySummary= |Advisory= |Recommendation..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="735" xml:space="preserve">&lt;noinclude&gt;
This is the "Advisory" template.
It should be called in the following format:
&lt;pre&gt;
{{Advisory
|ID=
|Handling=
|Title=
|AdvisorySummary=
|Advisory=
|Recommendations=
|Additional=
}}
&lt;/pre&gt;
Edit the page to see the template text.
&lt;/noinclude&gt;&lt;includeonly&gt;{| class="wikitable"
! Advisory Identifier
| [[Has label::{{{ID|}}}]] 
|-
! Sensitivity
| {{#arraymap:{{{Handling|}}}|,|x|[[Data Classification::x]]}}
|-
! Title
| [[Full Title::{{{Title|}}}]] 
|-
! Summary
| [[Has description::{{{AdvisorySummary|}}}]] 
|-
! Advisory
| [[Abstract::{{{Advisory|}}}]] 
|-
! Recommendations
| [[References::{{{Recommendations|}}}]] 
|-
! Additional Information
| [[Citation::{{{Additional|}}}]] 
|}

[[Category:Advisories]]
&lt;/includeonly&gt;</text>
    <sha1>758d6c5452eec45ae14c1cc20041211eec187c99</sha1>
  </revision>
</page>
<page arvcontinue="20160909091621|753">
  <title>Form:Advisory</title>
  <ns>106</ns>
  <id>341</id>
  <revision>
    <id>800</id>
    <timestamp>2022-05-11T08:56:16Z</timestamp>
    <contributor>
      <username>Tophatter</username>
      <id>5</id>
    </contributor>
    <comment>Created page with "&lt;noinclude&gt; This is the "Advisory" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edi..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1028" xml:space="preserve">&lt;noinclude&gt;
This is the "Advisory" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.


{{#forminput:form=Advisory}}

&lt;/noinclude&gt;&lt;includeonly&gt;
&lt;div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"&gt;&lt;/div&gt;
{{{for template|Advisory}}}
{| class="formtable"
! ID: 
| {{{field|ID}}}
|-
! Handling: 
| {{{field|Handling|input type=dropdown}}}
|-
! Title: 
| {{{field|Title}}}
|-
! AdvisorySummary: 
| {{{field|AdvisorySummary}}}
|-
! Advisory: 
| {{{field|Advisory}}}
|-
! Recommendations: 
| {{{field|Recommendations}}}
|-
! Additional: 
| {{{field|Additional}}}
|}
{{{end template}}}

'''Analyst Notes:'''

{{{standard input|Notes|rows=10}}}


{{{standard input|free text}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
&lt;/includeonly&gt;</text>
    <sha1>ece7fefaa8ca56977202675992ef08ee22867f10</sha1>
  </revision>
</page>
</mediawiki>